AI agents call get_my_lists 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 is a simple read/query operation that retrieves user's existing lists and their properties. It has no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an AI could only enumerate a user's lists, which is a low-severity information disclosure concern.
From the tool's definition Tool name 'get_my_lists' and description 'Get your Hardcover lists' indicate a retrieval operation with no side effects. Returns metadata (id, name, books count, privacy) without modifying data.
Attacks that exploit this kind of access
Get your Hardcover lists. Returns id, name, books count, privacy. 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_my_lists: 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_my_lists 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_my_lists 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_my_lists. 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_my_lists 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 →