get_spell_details
AI agents call get_spell_details to retrieve information from Remote MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests it retrieves spell information without modifying or executing anything. The sibling tools are all read operations (get_*, list_*, search_*), establishing a pattern of data retrieval. With no description, confidence is slightly reduced, but the contextual pattern strongly indicates a safe read operation.
From the tool's definition Tool name 'get_spell_details' combined with sibling tools ('get_class_details', 'get_entry', 'get_monster_stats', 'search_rules') indicates a read-only API for retrieving game/reference data.
Attacks that exploit this kind of access
get_spell_details. It is categorised as a Read tool in the Remote MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Remote MCP Server MCP server in PolicyLayer and add a rule for get_spell_details: 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 Remote MCP Server. Nothing to install.
get_spell_details 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_spell_details 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_spell_details. 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_spell_details is provided by the Remote MCP Server MCP server (robertsapunarich/mcp-ose). 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 →