Publish MCP version to Firebase so other users get update notifications. Call after pushing changes.
AI agents use publish_mcp_version to create or update resources in Planning Game — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Planning Game environment.
This tool creates or modifies data in Firebase (a cloud backend service). Publishing a version is a write operation that affects shared state visible to other users. It is not destructive (versions can be overwritten/replaced), not financial, and not arbitrary code execution.
From the tool's definition The tool 'publish_mcp_version' explicitly publishes/writes an MCP version to Firebase to enable update notifications. The description indicates data modification: 'Publish MCP version to Firebase so other users get update notifications.'
Attacks that exploit this kind of access
Publish MCP version to Firebase so other users get update notifications. Call after pushing changes. It is categorised as a Write tool in the Planning Game MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Planning Game MCP server in PolicyLayer and add a rule for publish_mcp_version: 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 Planning Game. Nothing to install.
publish_mcp_version 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 publish_mcp_version 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 publish_mcp_version. 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.
publish_mcp_version is provided by the Planning Game MCP server (planning-game-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 →