Get the social complexity score trajectory for a polity across centuries.
AI agents call get_complexity_timeline 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 and returns existing historical data from the Seshat Global History Databank without side effects. It performs a read-only retrieval of complexity metrics across time periods for a specified polity. No data creation, modification, deletion, or external code execution occurs.
From the tool's definition Tool retrieves historical social complexity score trajectory data ('Get the social complexity score trajectory'); no modification, deletion, or execution capabilities; purely informational query operation.
Attacks that exploit this kind of access
Get the social complexity score trajectory for a polity across centuries. 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 get_complexity_timeline: 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.
get_complexity_timeline 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 get_complexity_timeline 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 get_complexity_timeline. 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.
get_complexity_timeline 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 →