Low Risk

perception_manage

Operator

How to control perception_manage ↓

What perception_manage does on Rpg

AI agents call perception_manage as a supporting operation in Rpg workflows.

Low Risk

Why perception_manage needs a policy

The description 'Operator' is essentially empty and provides no meaningful information about what this tool does. The name 'perception_manage' in the context of an RPG game engine likely manages character perception checks or visibility states within the game world, which would be a Write operation at most. However, given the lack of descriptive information, confidence is very low.

From the tool's definition Tool name is 'perception_manage' with description only saying 'Operator' — uninformative description provides no detail about what the tool does.

Documented attack patterns abuse exactly the kind of access perception_manage gives an agent:

How to control perception_manage

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 perception_manage:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "perception_manage": {
      "limits": [
        {
          "counter": "perception_manage_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

perception_manage gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Rpg — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about perception_manage

What does the perception_manage tool do? +

Operator. It is categorised as a Other tool in the Rpg MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on perception_manage? +

Register the Rpg MCP server in PolicyLayer and add a rule for perception_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.

What risk level is perception_manage? +

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

Can I rate-limit perception_manage? +

Yes. Add a rate_limit block to the perception_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.

How do I block perception_manage completely? +

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

What MCP server provides perception_manage? +

perception_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.

Enforce policy on every Rpg tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.