update_control_status · Mipiti MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_control_status does on Mipiti MCP Server

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

WHY IT NEEDS A POLICY

Why update_control_status needs a policy

The tool modifies control status records within a security posture management platform, which is a reversible write operation. While the empty description limits precision, the naming convention and server context (threat models, controls, compliance mapping) suggest it updates control metadata rather than executing arbitrary operations or deleting data.

From the tool's definition Tool name 'update_control_status' combined with sibling tools like 'add_evidence', 'add_asset', 'apply_certain_reconciliation_match' indicates the server manages security posture data. The 'update_' prefix signals modification of existing records (controls).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_control_status Rate-limited

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

FAQ

Questions about update_control_status

What does the update_control_status tool do? +

update_control_status. It is categorised as a Write tool in the Mipiti 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 update_control_status? +

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

What risk level is update_control_status? +

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

Can I rate-limit update_control_status? +

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

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

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