AI agents use set_reading_goal to create or update resources in Hardcover — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hardcover environment.
This tool creates or updates reading goal metadata (target, metric, dates) in the user's library. These are reversible data modifications—the goal can be changed or deleted later—with no side effects beyond updating the user's own reading preferences. It falls squarely into the Write category (reversible data modification) rather than Read (query-only) or Execute (external operations).
From the tool's definition Tool description states 'Create or update a reading goal', indicating it modifies user data (reading goals) reversibly.
Attacks that exploit this kind of access
Create or update a reading goal with target, metric, dates, and optional. It is categorised as a Write tool in the Hardcover MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hardcover MCP server in PolicyLayer and add a rule for set_reading_goal: 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 Hardcover. Nothing to install.
set_reading_goal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_reading_goal 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 set_reading_goal. 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.
set_reading_goal is provided by the Hardcover MCP server (kristianedlund/hardcover-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 →