update_chore · CoupleHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_chore does on CoupleHub MCP Server

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

WHY IT NEEDS A POLICY

Why update_chore needs a policy

This tool modifies existing chore records (metadata like name, description, assignment, deadline, etc.) but does not delete or irreversibly destroy data. It is reversible because the previous state can be restored by updating again. The operation is non-destructive and operates on shared household data within a couples' app context.

From the tool's definition Tool description states 'Update a chore's metadata' – this is a modification operation. The phrase 'only include fields that need changing' indicates partial updates to existing records, which is reversible data modification typical of Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_chore Rate-limited

update_chore 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_chore": {
      "limits": [
        {
          "counter": "update_chore_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 CoupleHub MCP Server, so you can run agents against it safely.

FAQ

Questions about update_chore

What does the update_chore tool do? +

Update a chore's metadata. Only include fields that need changing. It is categorised as a Write tool in the CoupleHub 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_chore? +

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

What risk level is update_chore? +

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

Can I rate-limit update_chore? +

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

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

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