List all available agents in the playground that you can interact with.
AI agents call list_available_agents to retrieve information from Automagik Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available agents without creating, modifying, deleting, or executing any external operations. It has minimal blast radius: even if an AI agent calls it repeatedly, it only retrieves metadata. No data is altered, no commands are executed, and no financial or destructive consequences are possible.
From the tool's definition The tool description explicitly states 'List all available agents' — a retrieval operation with no modification or side effects. The verb 'list' is a canonical read operation.
Documented attack patterns abuse exactly the kind of access list_available_agents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for list_available_agents:
{
"version": "1",
"default": "deny",
"tools": {
"list_available_agents": {}
}
}list_available_agents is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available agents in the playground that you can interact with. It is categorised as a Read tool in the Automagik Tools MCP Server, which means it retrieves data without modifying state.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for list_available_agents: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Automagik Tools. Nothing to install.
list_available_agents is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_available_agents rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for list_available_agents. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
list_available_agents is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.