Search for countries by name.
AI agents call search_countries to retrieve information from SQLite Geography Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves geographical data without any side effects, modifications, or irreversible actions. It is a straightforward search/query operation that only reads from the SQLite database. The blast radius of misuse is minimal—an agent cannot harm systems, delete data, execute code, or cause financial damage by repeatedly or creatively calling a country name search.
From the tool's definition Tool description states 'Search for countries by name' — a query operation with no data modification. Server description confirms this is for 'exploration of geographical data' and 'searches by name'. All sibling tools (get_*) are read-only retrieval methods.
Attacks that exploit this kind of access
Search for countries by name. It is categorised as a Read tool in the SQLite Geography Server MCP Server, which means it retrieves data without modifying state.
Register the SQLite Geography Server MCP server in PolicyLayer and add a rule for search_countries: 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 SQLite Geography Server. Nothing to install.
search_countries 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 search_countries 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 search_countries. 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.
search_countries is provided by the SQLite Geography Server MCP server (pdichone/mcp-course-code). 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 →