update_statuses · kintone MCP Server (Python3) MCP

WHAT IT DOES

What update_statuses does on kintone MCP Server (Python3)

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

WHY IT NEEDS A POLICY

Why update_statuses needs a policy

This tool modifies record statuses but does not permanently delete data or execute arbitrary code. Status updates in workflow systems are typically reversible (statuses can be changed back), placing it in the Write category. Severity is medium because bulk updates to 100 records could impact business processes if misapplied, but the changes are not destructive or financial in nature.

From the tool's definition Tool description states 'Update the status of multiple records', indicating modification of existing data. The name 'update_statuses' and action verb 'Update' confirm this is a write operation that modifies record state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_statuses Rate-limited

update_statuses 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_statuses": {
      "limits": [
        {
          "counter": "update_statuses_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 kintone MCP Server (Python3), so you can run agents against it safely.

FAQ

Questions about update_statuses

What does the update_statuses tool do? +

Update the status of multiple records (max 100). It is categorised as a Write tool in the kintone MCP Server (Python3) 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_statuses? +

Register the kintone MCP Server (Python3) MCP server in PolicyLayer and add a rule for update_statuses: 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 kintone MCP Server (Python3). Nothing to install.

What risk level is update_statuses? +

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

Can I rate-limit update_statuses? +

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

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

update_statuses is provided by the kintone MCP Server (Python3) MCP server (r3-yamauchi/kintone-mcp-server-python3). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.