Low Risk

search_spells

Search for D&D 5E spells with various filters

Part of the Grimoire Spellbook Server server.

search_spells is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE GRIMOIRE SPELLBOOK SERVER →

Free to start. No card required.

AI agents call search_spells to retrieve information from Grimoire Spellbook Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though search_spells only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_spells": {}
  }
}

See the full Grimoire Spellbook Server policy for all 5 tools.

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

ENFORCE ON MY GRIMOIRE SPELLBOOK SERVER →

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

SECURE GRIMOIRE SPELLBOOK SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the search_spells tool do? +

Search for D&D 5E spells with various filters. It is categorised as a Read tool in the Grimoire Spellbook Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_spells? +

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

What risk level is search_spells? +

search_spells is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_spells? +

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

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

search_spells is provided by the Grimoire Spellbook Server MCP server (Linell/grimoire-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Grimoire Spellbook Server tool call.

Deterministic rules across all 5 Grimoire Spellbook Server 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.