Get status of all mounted servers and available workflows.
AI agents call hub_status to retrieve information from AI Producer Hub 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 the current status of servers and workflows. It performs no data modification, deletion, or external operations. The verb 'Get' and the passive nature of status reporting confirm this is a Read category tool with low severity, as it poses minimal risk even if queried by an AI agent—the worst outcome would be information disclosure of already-available system state.
From the tool's definition Tool name 'hub_status' and description 'Get status of all mounted servers and available workflows' indicate a read-only query operation that retrieves system state information without modification or side effects.
Attacks that exploit this kind of access
Get status of all mounted servers and available workflows. It is categorised as a Read tool in the AI Producer Hub MCP Server, which means it retrieves data without modifying state.
Register the AI Producer Hub MCP server in PolicyLayer and add a rule for hub_status: 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 AI Producer Hub. Nothing to install.
hub_status 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_status 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_status. 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_status is provided by the AI Producer Hub MCP server (sandraschi/ai-producer-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →