AI agents call list_jurisdictions to retrieve information from Regmd without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static reference data about regulatory jurisdictions without modifying any data, executing code, or triggering external side effects. It is a straightforward read operation that would provide informational context to users exploring the regulatory database. Misuse poses minimal risk as the output is reference information about supported jurisdictions.
From the tool's definition Tool name 'list_jurisdictions' and description 'List all supported regulatory jurisdictions with details. Returns jurisdiction codes, full names, regulatory agencies, and supported features.' indicate a retrieval operation that queries and returns…
Attacks that exploit this kind of access
List all supported regulatory jurisdictions with details. Returns jurisdiction codes, full names, regulatory agencies, and supported features. It is categorised as a Read tool in the Regmd MCP Server, which means it retrieves data without modifying state.
Register the Regmd MCP server in PolicyLayer and add a rule for list_jurisdictions: 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 Regmd. Nothing to install.
list_jurisdictions 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_jurisdictions 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_jurisdictions. 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_jurisdictions is provided by the Regmd MCP server (zubi-wiz/regmd-mcp). 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 →