run_counterfactual_estimate · Seshat MCP Server MCP

WHAT IT DOES

What run_counterfactual_estimate does on Seshat MCP Server

AI agents invoke run_counterfactual_estimate to trigger actions in Seshat MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_counterfactual_estimate needs a policy

This tool runs complex historical-demographic simulations or predictive models that execute based on arbitrary arguments (polity selection, injection year, variable modifications). While it does not modify the underlying databank (thus not Write/Destructive) nor move money (thus not Financial), it executes a non-trivial computational operation whose results depend entirely on user-provided parameters.

From the tool's definition Tool description states it 'projects' outcomes based on injected parameters into historical data models. The term 'counterfactual estimate' combined with 'Given a polity, an injection year, and variable changes, projects' indicates the tool executes a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_counterfactual_estimate Rate-limited

run_counterfactual_estimate stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_counterfactual_estimate": {
      "limits": [
        {
          "counter": "run_counterfactual_estimate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Seshat MCP Server, so you can run agents against it safely.

FAQ

Questions about run_counterfactual_estimate

What does the run_counterfactual_estimate tool do? +

Core estimation tool. Given a polity, an injection year, and variable changes, projects. It is categorised as a Execute tool in the Seshat MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_counterfactual_estimate? +

Register the Seshat MCP Server MCP server in PolicyLayer and add a rule for run_counterfactual_estimate: 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.

What risk level is run_counterfactual_estimate? +

run_counterfactual_estimate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_counterfactual_estimate? +

Yes. Add a rate_limit block to the run_counterfactual_estimate 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.

How do I block run_counterfactual_estimate completely? +

Set action: deny in the PolicyLayer policy for run_counterfactual_estimate. 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.

What MCP server provides run_counterfactual_estimate? +

run_counterfactual_estimate 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.