Search for historical polities (societies, states, empires) in the Seshat Global History Databank.
AI agents call search_polities to retrieve information from Seshat MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a historical database to find polities but does not modify, delete, or execute any operations. It returns information only. The data is historical and non-financial. Blast radius of misuse is minimal (e.g., spam queries, but no harm to data or external systems).
From the tool's definition Tool description states 'Search for historical polities' — a retrieval operation with no indication of modification, deletion, or execution of external operations. The name contains 'search', a classic read verb.
Attacks that exploit this kind of access
Search for historical polities (societies, states, empires) in the Seshat Global History Databank. It is categorised as a Read tool in the Seshat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Seshat MCP Server MCP server in PolicyLayer and add a rule for search_polities: 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 Seshat MCP Server. Nothing to install.
search_polities 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_polities 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_polities. 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_polities is provided by the Seshat MCP Server MCP server (mosse/seshat-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 →