Download guidelines from Firebase and write them as local files. Compares versions to only update changed guidelines.
AI agents use sync_guidelines 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.
The tool downloads remote data (guidelines from Firebase) and persists it locally by writing/updating files. This is a Write operation because it modifies local state reversibly—guidelines can be re-synced or deleted. It's not Execute because no arbitrary code/commands are run; it's not Destructive because updates are reversible (old versions can be restored via re-sync).
From the tool's definition Tool description states it 'write[s] them as local files' and 'update[s] changed guidelines'. These are explicit write operations that create or modify local file system state.
Attacks that exploit this kind of access
Download guidelines from Firebase and write them as local files. Compares versions to only update changed guidelines. 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 sync_guidelines: 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.
sync_guidelines 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 sync_guidelines 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 sync_guidelines. 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.
sync_guidelines 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 →