Get detailed information about the hub and available tools
AI agents call hub_info 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 retrieves and queries information about the hub and its available tools. It performs a GET-like operation that does not create, modify, delete, execute code, or trigger external operations. The read-only nature and informational purpose make this a Read category tool with low severity, as it has minimal blast radius if misused by an agent.
From the tool's definition Tool name 'hub_info' and description 'Get detailed information about the hub and available tools' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access hub_info 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 hub_info:
{
"version": "1",
"default": "deny",
"tools": {
"hub_info": {}
}
}hub_info 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.
Get detailed information about the hub and available tools. 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 hub_info: 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.
hub_info 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 hub_info 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 hub_info. 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.
hub_info 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.