upsert_location
AI agents use upsert_location to create or update resources in RPG Ledger MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RPG Ledger MCP Server environment.
Upsert (update/insert) operations create or modify data reversibly—they do not delete or destroy data, making this Write rather than Destructive. The empty description lowers confidence slightly, but the tool name itself and server context (RPG campaign state management) clearly indicate a write-class mutation.
From the tool's definition Tool name 'upsert_location' indicates an update-or-insert operation on location data. Sibling tools include 'create_campaign', 'create_character', and 'delete_location', confirming this server manages mutable game state.
Attacks that exploit this kind of access
upsert_location. It is categorised as a Write tool in the RPG Ledger MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RPG Ledger MCP Server MCP server in PolicyLayer and add a rule for upsert_location: 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 Ledger MCP Server. Nothing to install.
upsert_location 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 upsert_location 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 upsert_location. 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.
upsert_location is provided by the RPG Ledger MCP Server MCP server (sepa79/rpg-ledger-mcp). 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 →