set_status · Interagent MCP: Risk & Policy

WHAT IT DOES

What set_status does on Interagent

AI agents use set_status to create or update resources in Interagent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Interagent environment.

WHY IT NEEDS A POLICY

Why set_status needs a policy

This tool writes/updates agent status metadata in a shared coordination system. It has no destructive, financial, or code-execution side effects. The write is reversible (status can be updated again), and the blast radius is minimal — an incorrect status only affects visibility and coordination signals between agents, not critical data or operations.

From the tool's definition Tool description states 'Set your current working status' — this modifies (writes) the status field that other agents can read, creating or updating a data record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_status Rate-limited

set_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_status": {
      "limits": [
        {
          "counter": "set_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about set_status

What does the set_status tool do? +

Set your current working status so other agents can see what you. It is categorised as a Write tool in the Interagent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_status? +

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

What risk level is set_status? +

set_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_status? +

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

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

set_status is provided by the Interagent MCP server (signalclaude/interagent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.