jambonz_developer_toolkit
AI agents call jambonz_developer_toolkit 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.
This tool provides access to developer documentation, schema definitions, and examples without modifying data or executing operations. All operations are informational queries with no side effects. The sibling tools confirm a pattern of read-only schema and documentation retrieval. Classified as Read with low severity due to lack of blast radius from misuse.
From the tool's definition Tool is part of a schema server that 'exposes jambonz verb schemas and developer documentation as MCP tools, enabling AI agents to query verb definitions, component types, callback payloads, and the full developer guide.' Sibling tools include…
Attacks that exploit this kind of access
jambonz_developer_toolkit. 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 jambonz_developer_toolkit: 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.
jambonz_developer_toolkit 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 jambonz_developer_toolkit 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 jambonz_developer_toolkit. 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.
jambonz_developer_toolkit 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 →