Medium Risk

add_to_reading_list

Add a book to a reading list

Part of the Spines server.

add_to_reading_list can modify Spines data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SPINES →

Free to start. No card required.

AI agents use add_to_reading_list to create or modify resources in Spines. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call add_to_reading_list repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Spines.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_to_reading_list": {
      "limits": [
        {
          "counter": "add_to_reading_list_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Spines policy for all 18 tools.

Get this rule live on your own Spines server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SPINES →

View all 18 tools →

These attack patterns abuse exactly the kind of access add_to_reading_list gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so add_to_reading_list only ever does what you allow.

SECURE SPINES →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the add_to_reading_list tool do? +

Add a book to a reading list. It is categorised as a Write tool in the Spines MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_to_reading_list? +

Register the Spines MCP server in PolicyLayer and add a rule for add_to_reading_list: 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 Spines. Nothing to install.

What risk level is add_to_reading_list? +

add_to_reading_list is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_to_reading_list? +

Yes. Add a rate_limit block to the add_to_reading_list 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.

How do I block add_to_reading_list completely? +

Set action: deny in the PolicyLayer policy for add_to_reading_list. 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.

What MCP server provides add_to_reading_list? +

add_to_reading_list is provided by the Spines MCP server (@spines/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Spines tool call.

Deterministic rules across all 18 Spines tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.