Manage area-effect auras (Spirit Guardians, Aura of Protection, etc.). Actions: create, list, get_affecting, process, remove, remove_by_owner, expire Aliases: new→create, active→list, affecting→get_affecting, trigger→process, end→remove AURA TARGETS: - affectsSelf: affects the caster - affectsAll...
AI agents use aura_manage to create or update resources in Rpg — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rpg environment.
The tool creates, modifies, and removes aura records in a persistent database. While 'remove' and 'expire' could seem destructive, these are reversible game-state changes within a session context (auras are transient game mechanics, not permanent data loss). The dominant operations are write-style mutations to game state.
From the tool's definition Actions: create, list, get_affecting, process, remove, remove_by_owner, expire — manages persistent aura state (create/remove/expire) in SQLite-backed game engine
Documented attack patterns abuse exactly the kind of access aura_manage gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rpg, and nothing reaches the server without passing your rules. This is the rule we recommend for aura_manage:
{
"version": "1",
"default": "deny",
"tools": {
"aura_manage": {
"limits": [
{
"counter": "aura_manage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}aura_manage 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.
Free to start. No card required.
Manage area-effect auras (Spirit Guardians, Aura of Protection, etc.). Actions: create, list, get_affecting, process, remove, remove_by_owner, expire Aliases: new→create, active→list, affecting→get_affecting, trigger→process, end→remove AURA TARGETS: - affectsSelf: affects the caster - affectsAllies: affects allied creatures - affectsEnemies: affects enemy creatures EFFECT TRIGGERS: - enter: when creature enters aura - exit: when creature exits aura - start_of_turn: at start of creature. It is categorised as a Write tool in the Rpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rpg MCP server in PolicyLayer and add a rule for aura_manage: 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 Rpg. Nothing to install.
aura_manage 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 aura_manage 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 aura_manage. 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.
aura_manage is provided by the Rpg MCP server (mnehmos/mnehmos.rpg.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rpg, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 Rpg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.