AI agents use push_to_notion to create or update resources in Kindle — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kindle environment.
This tool creates new pages/records in a Notion database, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), handle financial transactions (Financial), or merely retrieve data (Read).
From the tool's definition Tool description states it 'Push[es] a generated book summary to a Notion database as a structured page', which creates new records in an external service (Notion).
Attacks that exploit this kind of access
Push a generated book summary to a Notion database as a structured page. Call this once per book after generating each summary. It is categorised as a Write tool in the Kindle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kindle MCP server in PolicyLayer and add a rule for push_to_notion: 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 Kindle. Nothing to install.
push_to_notion 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 push_to_notion 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 push_to_notion. 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.
push_to_notion is provided by the Kindle MCP server (silcfcr/kindle-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 →