identify_magic
Resolve a real prepared Identify cast on one magic item. The caster must hold or wear it as intended, begin within one hour per magic-user level of first coming within 5ft, possess and consume a 100gp pearl, and spend one prepared Identify. The one-turn cast durably advances campaign time and tem...
This record as markdown: /tools/torch-to-crown/identify-magic.md
What identify_magic does on Torch-to-Crown
AI agents use identify_magic to create or update resources in Torch-to-Crown, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Torch-to-Crown environment.
Why identify_magic is rated Medium
An AI agent can call identify_magic faster than any human can review: one bad instruction and it creates or modifies resources in Torch-to-Crown by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs identify_magic safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Torch-to-Crown, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For identify_magic, this is the rule to start with:
identify_magic stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Torch-to-Crown, apply this rule, and every identify_magic call is checked against it from then on.
Questions about identify_magic
Resolve a real prepared Identify cast on one magic item. The caster must hold or wear it as intended, begin within one hour per magic-user level of first coming within 5ft, possess and consume a 100gp pearl, and spend one prepared Identify. The one-turn cast durably advances campaign time and temporarily costs 8 Constitution, recovered only by rest. Each duration segment makes the printed 15% + 5%/level insight check. Omit item and actor only for a non-mutating odds preview. It is categorised as a Write tool in the Torch-to-Crown MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Torch-to-Crown MCP server in PolicyLayer and add a rule for identify_magic: 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 Torch-to-Crown. Nothing to install.
identify_magic 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 identify_magic 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 identify_magic. 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.
identify_magic is provided by the Torch-to-Crown MCP server (Diogenes187/Torch-to-Crown). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Torch-to-Crown, and thousands of servers like it.
This server
Across the catalogue