update_project_state · Project Creator MCP: Risk & Policy

WHAT IT DOES

What update_project_state does on Project Creator MCP

AI agents use update_project_state to create or update resources in Project Creator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Creator MCP environment.

WHY IT NEEDS A POLICY

Why update_project_state needs a policy

The tool name and context suggest it modifies project state reversibly. While the description is empty (lowering confidence slightly), the naming convention and sibling tools that write to the file system indicate this performs Write operations. It is not Destructive because 'update' implies modification rather than deletion, and no evidence suggests financial impact or arbitrary code execution.

From the tool's definition Tool name 'update_project_state' indicates modification of project state; sibling tools include destructive operations (delete_file) and file system modifications (create_file, create_directory, copy_file_or_directory), establishing a pattern where state…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project_state Rate-limited

update_project_state stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_project_state": {
      "limits": [
        {
          "counter": "update_project_state_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Project Creator MCP, so you can run agents against it safely.

FAQ

Questions about update_project_state

What does the update_project_state tool do? +

update_project_state. It is categorised as a Write tool in the Project Creator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_project_state? +

Register the Project Creator MCP server in PolicyLayer and add a rule for update_project_state: 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 Project Creator MCP. Nothing to install.

What risk level is update_project_state? +

update_project_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_project_state? +

Yes. Add a rate_limit block to the update_project_state 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.

How do I block update_project_state completely? +

Set action: deny in the PolicyLayer policy for update_project_state. 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.

What MCP server provides update_project_state? +

update_project_state is provided by the Project Creator MCP server (jackalterman/project-creator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.