get_chores
AI agents call get_chores 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 tool appears to retrieve or query existing chore data without modifying it. The 'get_' prefix conventionally denotes read-only operations. Confidence is slightly reduced due to the empty description, but the naming convention and context from sibling tools provide sufficient evidence for a Read classification.
From the tool's definition Tool name 'get_chores' follows the standard read operation pattern (get_*). No description provided, but the name strongly indicates a retrieval operation.
Attacks that exploit this kind of access
get_chores. 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_chores: 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_chores 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_chores 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_chores. 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_chores 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 →