Governed ability

Get site info

aafm/get-site-info Read only

Retrieve the site name, tagline, URL, and language.

How it is governed

The same model as every ability in the plugin, stated for this one.

  • Off until you enable it

    Like every ability, Get site info ships switched off. You turn it on one at a time, and an update never widens access on its own.

  • Reads only

    It reads data and returns it to your client. Nothing on your site is created, changed, or removed.

  • Capability gated

    A connection only sees Get site info if the user you connected can run it, and the plugin checks that capability again before it executes.

  • Every call audited

    The call is written to the log in your own database, denials included, with the argument keys but never the values.

See it in action

An illustrative run. Your real calls and data stay on your own site.

agent-abilities · audit Governed
You Get site info on this site.
Run Running aafm/get-site-info
Gate Allowed read capability confirmed
Audit aafm/get-site-info · principal: editor · args: keys
Result Returns the data the agent asked for. Nothing on the site changes.

Try it with a prompt

Example requests you could paste to your agent.

  1. What is this site's name, tagline, and URL?
  2. Tell me which language the site is set to.
  3. Give me the basic site info: title, description, and address.

These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.

Frequently asked

Short answers for Get site info.

What does it return?

The site name, tagline, URL, and language. It is a small read-only summary.

How is this different from Get site settings?

Get site info includes the site URL and language, while Get site settings covers formatting options like timezone and posts per page and deliberately leaves out the URL. Both are read only and off by default.

Back to all abilities

Governed by default, from the first call.

Get site info is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.

Every ability off until you enable it, capability-gated on every call.