reevaluate_chore_points · CoupleHub MCP Server MCP

WHAT IT DOES

What reevaluate_chore_points does on CoupleHub MCP Server

AI agents use reevaluate_chore_points 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 reevaluate_chore_points needs a policy

The tool appears to update or recalculate chore point values based on its name. This is a reversible modification to shared household management data, fitting the Write category. Severity is low because chore points in a couple's app have limited blast radius—no financial impact, no deletion, and easily correctable.

From the tool's definition Tool name 'reevaluate_chore_points' suggests modifying chore-related data (points/scoring). No description provided. Context shows sibling tools like 'create_chore' and 'complete_chore' are Write operations on shared household data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reevaluate_chore_points Rate-limited

reevaluate_chore_points 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": {
    "reevaluate_chore_points": {
      "limits": [
        {
          "counter": "reevaluate_chore_points_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 reevaluate_chore_points

What does the reevaluate_chore_points tool do? +

reevaluate_chore_points. 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 reevaluate_chore_points? +

Register the CoupleHub MCP Server MCP server in PolicyLayer and add a rule for reevaluate_chore_points: 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 reevaluate_chore_points? +

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

Can I rate-limit reevaluate_chore_points? +

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

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

reevaluate_chore_points 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.