Critical Risk →

remove_book_from_library

Remove a book from your library. Requires authorization.

Part of the SansFiction server.

remove_book_from_library can permanently delete data in SansFiction, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SANSFICTION →

Free to start. No card required.

AI agents may call remove_book_from_library to permanently remove or destroy resources in SansFiction. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call remove_book_from_library in a loop, permanently destroying resources in SansFiction. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_book_from_library"
  ]
}

See the full SansFiction policy for all 16 tools.

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

ENFORCE ON MY SANSFICTION →

View all 16 tools →

These attack patterns abuse exactly the kind of access remove_book_from_library 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 remove_book_from_library only ever does what you allow.

SECURE SANSFICTION →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the remove_book_from_library tool do? +

Remove a book from your library. Requires authorization.. It is categorised as a Destructive tool in the SansFiction MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_book_from_library? +

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

What risk level is remove_book_from_library? +

remove_book_from_library is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_book_from_library? +

Yes. Add a rate_limit block to the remove_book_from_library 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 remove_book_from_library completely? +

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

remove_book_from_library is provided by the SansFiction MCP server (hello-uvza/sansfiction). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SansFiction tool call.

Deterministic rules across all 16 SansFiction 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.