list_jambonz_tools
AI agents call list_jambonz_tools to retrieve information from Mcp Schema without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' operation retrieves or enumerates tools/schemas without side effects. The server's stated purpose is to expose documentation and enable querying of definitions—purely informational access. No evidence of write, execute, or destructive capabilities. Confidence is high despite empty tool description due to clear naming convention and server context.
From the tool's definition Tool name 'list_jambonz_tools' with 'list' verb indicates retrieval without modification. Server purpose states it 'exposes jambonz verb schemas and developer documentation' and enables AI agents to 'query verb definitions' and access 'the full developer…
Attacks that exploit this kind of access
list_jambonz_tools. It is categorised as a Read tool in the Mcp Schema MCP Server, which means it retrieves data without modifying state.
Register the Mcp Schema MCP server in PolicyLayer and add a rule for list_jambonz_tools: 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 Mcp Schema. Nothing to install.
list_jambonz_tools 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_jambonz_tools 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_jambonz_tools. 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_jambonz_tools is provided by the Mcp Schema MCP server (jambonz/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 →