session_respond · Managed Agent Control MCP: Risk & Policy

WHAT IT DOES

What session_respond does on Managed Agent Control

AI agents invoke session_respond to trigger actions in Managed Agent Control. 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 session_respond needs a policy

Based on the server description, this tool likely sends a response or approval to a running agent session, which can trigger further agent actions or tool executions. The empty description lowers confidence, but the server context strongly implies this causes external operations. Approving tool runs could have cascading effects, placing this in Execute at high severity.

From the tool's definition Tool name 'session_respond' on a server that allows replying to agents and approving tools they want to run; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

session_respond Rate-limited

session_respond 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": {
    "session_respond": {
      "limits": [
        {
          "counter": "session_respond_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 Managed Agent Control, so you can run agents against it safely.

FAQ

Questions about session_respond

What does the session_respond tool do? +

session_respond. It is categorised as a Execute tool in the Managed Agent Control MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on session_respond? +

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

What risk level is session_respond? +

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

Can I rate-limit session_respond? +

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

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

session_respond is provided by the Managed Agent Control MCP server (modus-agendi/managed-agent-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

session_respond is one line of Managed Agent Control's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →