AI agents use place_prop to create or update resources in ChatRPG — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ChatRPG environment.
This tool creates or modifies battlefield props, which is a reversible change to game state. It does not execute arbitrary code, delete data permanently, move money, or retrieve information passively. 'Manage' suggests potential updates to existing props.
From the tool's definition The tool description states it can "Place or manage interactive props on the battlefield" — 'place' and 'manage' are write operations that create or modify game state objects (props) reversibly within the game world.
Attacks that exploit this kind of access
Place or manage interactive props on the battlefield (barrels, doors, chests, etc.). It is categorised as a Write tool in the ChatRPG MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ChatRPG MCP server in PolicyLayer and add a rule for place_prop: 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 ChatRPG. Nothing to install.
place_prop 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 place_prop 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 place_prop. 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.
place_prop is provided by the ChatRPG MCP server (mnehmos/mnehmos.chatrpg.game). 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 →