AI agents use add_journal_entry 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 a new journal entry (a note or quote), which is a reversible write operation. It does not delete, execute code, trigger external systems, or involve financial transactions. The blast radius of misuse is minimal—unwanted journal entries can be deleted via the sibling 'delete_journal_entry' tool.
From the tool's definition Tool name 'add_journal_entry' and description 'Create a reading journal entry' explicitly indicate creation of new data.
Attacks that exploit this kind of access
Create a reading journal entry (for example a note or quote) for a book. 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 add_journal_entry: 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.
add_journal_entry 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 add_journal_entry 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 add_journal_entry. 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.
add_journal_entry 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 →