indexfoundry_serve_stop · IndexFoundry MCP: Risk & Policy

WHAT IT DOES

What indexfoundry_serve_stop does on IndexFoundry MCP

AI agents invoke indexfoundry_serve_stop to trigger actions in IndexFoundry MCP. 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 indexfoundry_serve_stop needs a policy

Stopping a running server is an execute-category action because it triggers external operational effects (halting a service). While not destructive (the server can be restarted) or irreversible, it causes a definite state change by terminating a process. Severity is medium because stopping an API server disrupts availability and may impact dependent systems, but is recoverable.

From the tool's definition Tool 'indexfoundry_serve_stop' actively stops a running process (a search API server). The action terminates an external operation in progress.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

indexfoundry_serve_stop Rate-limited

indexfoundry_serve_stop 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": {
    "indexfoundry_serve_stop": {
      "limits": [
        {
          "counter": "indexfoundry_serve_stop_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 IndexFoundry MCP, so you can run agents against it safely.

FAQ

Questions about indexfoundry_serve_stop

What does the indexfoundry_serve_stop tool do? +

Stop a running search API server for a run. Returns server uptime and request count. It is categorised as a Execute tool in the IndexFoundry MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on indexfoundry_serve_stop? +

Register the IndexFoundry MCP server in PolicyLayer and add a rule for indexfoundry_serve_stop: 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 IndexFoundry MCP. Nothing to install.

What risk level is indexfoundry_serve_stop? +

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

Can I rate-limit indexfoundry_serve_stop? +

Yes. Add a rate_limit block to the indexfoundry_serve_stop 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 indexfoundry_serve_stop completely? +

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

indexfoundry_serve_stop is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.