AI agents call policy_list to retrieve information from Musubix 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 existing policy data without modifying, deleting, or executing operations. Listing operations are read-only with minimal blast radius—exposure could leak policy information but cannot cause destructive or financial harm.
From the tool's definition Tool name 'policy_list' and description 'List all registered policies' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all registered policies. It is categorised as a Read tool in the Musubix MCP Server, which means it retrieves data without modifying state.
Register the Musubix MCP server in PolicyLayer and add a rule for policy_list: 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 Musubix. Nothing to install.
policy_list 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 policy_list 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 policy_list. 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.
policy_list is provided by the Musubix MCP server (@nahisaho/musubix-mcp-server). 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 →