state_put · Onboarded MCP Server MCP: Risk & Policy

WHAT IT DOES

What state_put does on Onboarded MCP Server

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

WHY IT NEEDS A POLICY

Why state_put needs a policy

This tool modifies state by storing entity references. It is a Write operation because it creates or modifies data reversibly—state can be updated or cleared later (as evidenced by the sibling tool 'state_delete'). It does not execute arbitrary code, delete data irreversibly, or move money.

From the tool's definition Tool name is 'state_put' and description states 'Store an entity reference (e.g., after creating via API)'. The verb 'store' indicates data is being written/persisted to state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

state_put Rate-limited

state_put 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": {
    "state_put": {
      "limits": [
        {
          "counter": "state_put_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 Onboarded MCP Server, so you can run agents against it safely.

FAQ

Questions about state_put

What does the state_put tool do? +

Store an entity reference (e.g., after creating via API). It is categorised as a Write tool in the Onboarded MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on state_put? +

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

What risk level is state_put? +

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

Can I rate-limit state_put? +

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

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

state_put is provided by the Onboarded MCP Server MCP server (onboardedinc/onboarded-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.