Get full source code for an SDK example. Available: ${sdkExampleNames.join(
AI agents call get_sdk_example 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 tool retrieves pre-existing SDK example source code, which is a documentation/reference operation with no side effects, data modification, or code execution. It falls clearly into the Read category. Severity is low because exposing code examples poses minimal risk—an AI agent querying this tool cannot cause harm through retrieval of static documentation.
From the tool's definition Tool name and description indicate retrieval of source code examples: 'Get full source code for an SDK example.' This is a read-only operation that queries and returns documentation artifacts without modifying or executing anything.
Attacks that exploit this kind of access
Get full source code for an SDK example. Available: ${sdkExampleNames.join(. 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 get_sdk_example: 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.
get_sdk_example 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 get_sdk_example 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 get_sdk_example. 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.
get_sdk_example 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 →