get_chore_scores
AI agents call get_chore_scores to retrieve information from CoupleHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix combined with lack of destructive action verbs indicates a retrieval operation. The tool queries chore score data for a shared couples management system, presenting minimal risk if misused—it only exposes information already accessible to authorized household members. The empty description slightly reduces confidence, but the naming pattern is clear.
From the tool's definition Tool name 'get_chore_scores' with 'get' prefix; sibling tools include create, delete, and complete operations suggesting this retrieves data about chore scores without modification.
Attacks that exploit this kind of access
get_chore_scores. It is categorised as a Read tool in the CoupleHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CoupleHub MCP Server MCP server in PolicyLayer and add a rule for get_chore_scores: 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.
get_chore_scores is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_chore_scores 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.
Set action: deny in the PolicyLayer policy for get_chore_scores. 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.
get_chore_scores 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →