List all municipalities in a state that use Municode
AI agents call list_municipalities to retrieve information from MunicipalMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries publicly available municipal information with no side effects. It falls clearly into the Read category as it only returns data about which municipalities are available in a given state. The blast radius of misuse is minimal — an agent could only enumerate municipalities, not modify any codes, execute operations, or cause harm. Severity is low.
From the tool's definition Tool description states it 'List all municipalities in a state that use Municode' — a retrieval operation with no modification, deletion, or execution capability. The action is purely informational (list/get pattern).
Attacks that exploit this kind of access
List all municipalities in a state that use Municode. It is categorised as a Read tool in the MunicipalMCP MCP Server, which means it retrieves data without modifying state.
Register the Municipal MCP server in PolicyLayer and add a rule for list_municipalities: 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 MunicipalMCP. Nothing to install.
list_municipalities 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 list_municipalities 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 list_municipalities. 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.
list_municipalities is provided by the Municipal MCP server (skatterbrainz/municipalmcp). 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 →