Check if a described scenario complies with building codes
AI agents call check_code_compliance 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 performs informational lookups and compliance validation without modifying any data, executing external code, or causing side effects. It reads building code data and returns compliance assessments. No data is created, deleted, or modified; no external operations are triggered.
From the tool's definition The tool name is 'check_code_compliance' and description states 'Check if a described scenario complies with building codes'. This is a query/lookup operation that retrieves and evaluates code information against a provided scenario.
Attacks that exploit this kind of access
Check if a described scenario complies with building codes. 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 check_code_compliance: 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.
check_code_compliance 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 check_code_compliance 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 check_code_compliance. 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.
check_code_compliance 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 →