Retrieve specific code section by exact reference (e.g.,
AI agents call get_code_section to retrieve information from DIY Helper MCP Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns static reference data (building codes like NEC, IRC, IPC) without modifying, executing, or deleting anything. It is a straightforward query operation that retrieves compliance documentation for user reference during DIY projects. Misuse poses minimal risk—an AI agent cannot cause damage by reading code sections.
From the tool's definition Tool name 'get_code_section' and description 'Retrieve specific code section' indicates a retrieval operation with no side effects. The action is to fetch building code reference information.
Attacks that exploit this kind of access
Retrieve specific code section by exact reference (e.g.,. It is categorised as a Read tool in the DIY Helper MCP Servers MCP Server, which means it retrieves data without modifying state.
Register the DIY Helper MCP Servers MCP server in PolicyLayer and add a rule for get_code_section: 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 DIY Helper MCP Servers. Nothing to install.
get_code_section 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_code_section 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_code_section. 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_code_section is provided by the DIY Helper MCP Servers MCP server (jrszilard/diy-helper-mcp-servers). 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 →