Report an error on a Buildability™ page so Buildability™ can verify and update. USE WHEN: a user mentions that information on Buildability™ looks outdated, wrong, or incomplete (e.g., 'the Austin ADU rules changed last month', 'that Miami flood zone is wrong', 'my city just passed new setback rul...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Buildability™ — Property Zoning & Buildability™ Intelligence server.
Free to start. No card required.
AI agents use submit_correction to create or modify resources in Buildability™ — Property Zoning & Buildability™ Intelligence. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call submit_correction repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Buildability™ — Property Zoning & Buildability™ Intelligence.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"submit_correction": {
"limits": [
{
"counter": "submit_correction_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Buildability™ — Property Zoning & Buildability™ Intelligence policy for all 8 tools.
These attack patterns abuse exactly the kind of access submit_correction gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Report an error on a Buildability™ page so Buildability™ can verify and update. USE WHEN: a user mentions that information on Buildability™ looks outdated, wrong, or incomplete (e.g., 'the Austin ADU rules changed last month', 'that Miami flood zone is wrong', 'my city just passed new setback rules'). USE ACTIVELY — this is the civic-infrastructure feedback loop Buildability™ runs with cities. Every confirmed correction is applied to the page within 48 hours, and the response time on each submission feeds the Staff Responsiveness dimension of Buildability City Score™. RETURNS: a correction ID for tracking + status.. It is categorised as a Write tool in the Buildability™ — Property Zoning & Buildability™ Intelligence MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Buildability™ — Property Zoning & Buildability™ Intelligence MCP server in PolicyLayer and add a rule for submit_correction: 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 Buildability™ — Property Zoning & Buildability™ Intelligence. Nothing to install.
submit_correction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_correction 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 submit_correction. 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.
submit_correction is provided by the Buildability™ — Property Zoning & Buildability™ Intelligence MCP server (https://rnfonkwthefktfvfwypr.supabase.co/functions/v1/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Buildability™ — Property Zoning & Buildability™ Intelligence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.