iso.subdivision
ISO 3166-2 subdivision lookup (states/provinces/regions). Pass code (US-CA) to resolve one → name + country, or country (2-letter, US) to list all its subdivisions with codes. Bundled authoritative ISO 3166-2 data (~3.8k subdivisions, 237 countries).
This record as markdown: /tools/io-github-2s-io-mcp/iso.subdivision.md
What iso.subdivision does on Mcp
AI agents call iso.subdivision to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why iso.subdivision is rated Low
This tool retrieves static, authoritative geographic reference data (ISO standard subdivision codes and names). It has no side effects, cannot modify data, and presents no financial or destructive capabilities. The risk is minimal since misuse would only return geographic information. The low severity reflects that even an agent querying this tool repeatedly would cause no harm.
From the tool's definition Tool performs 'lookup' and 'list' operations on read-only ISO 3166-2 subdivision data. No modifications, deletions, or external state changes.
Attacks that exploit this kind of access
The rule that runs iso.subdivision safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For iso.subdivision, this is the rule to start with:
iso.subdivision is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every iso.subdivision call is checked against it from then on.
Questions about iso.subdivision
ISO 3166-2 subdivision lookup (states/provinces/regions). Pass code (US-CA) to resolve one → name + country, or country (2-letter, US) to list all its subdivisions with codes. Bundled authoritative ISO 3166-2 data (~3.8k subdivisions, 237 countries). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for iso.subdivision: 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 Mcp. Nothing to install.
iso.subdivision 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 iso.subdivision 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 iso.subdivision. 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.
iso.subdivision is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue