AI agents call get_reading_journal to retrieve information from Hardcover without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing data (reading journal entries) belonging to the authenticated user without creating, modifying, or deleting anything. It is a straightforward data query operation with no side effects, fitting the Read category. The severity is low because misuse would only expose personal reading data, which is an information disclosure risk rather than a system-level threat.
From the tool's definition Tool name is 'get_reading_journal' and description states 'Fetch reading journal entries for the authenticated user.' The verb 'Fetch' and the read-only nature of retrieving existing journal entries indicate no data modification or side effects.
Attacks that exploit this kind of access
Fetch reading journal entries for the authenticated user. It is categorised as a Read tool in the Hardcover MCP Server, which means it retrieves data without modifying state.
Register the Hardcover MCP server in PolicyLayer and add a rule for get_reading_journal: 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.
get_reading_journal 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_reading_journal 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_reading_journal. 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_reading_journal 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 →