Update fields of an existing project (description, repoUrl, languages, frameworks, agentsGuidelines, etc.)
AI agents use update_project 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 reversibly. An AI agent could misuse it by altering project configurations, URLs, or guidelines in ways that affect project integrity or mislead team members, but changes are not irreversible (can be updated again).
From the tool's definition Tool name 'update_project' and description 'Update fields of an existing project' indicates modification of existing data. The tool modifies project metadata (description, repoUrl, languages, frameworks, agentsGuidelines) but does not delete or destroy data.
Attacks that exploit this kind of access
Update fields of an existing project (description, repoUrl, languages, frameworks, agentsGuidelines, etc.). 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 update_project: 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.
update_project 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 update_project 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 update_project. 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.
update_project 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 →