update-project · Things App MCP: Risk & Policy

WHAT IT DOES

What update-project does on Things App MCP

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

WHY IT NEEDS A POLICY

Why update-project needs a policy

This tool modifies data (project details) reversibly. A user can undo or re-modify the project afterward, so it does not irreversibly delete data (not Destructive). It does not execute arbitrary code or trigger external side effects unpredictably (not Execute).

From the tool's definition Tool name 'update-project' and description explicitly states 'Update an existing project' — a modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-project Rate-limited

update-project 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": {
      "limits": [
        {
          "counter": "update-project_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 Things App MCP, so you can run agents against it safely.

FAQ

Questions about update-project

What does the update-project tool do? +

Update an existing project in Things. Requires the project ID and your Things auth-token. It is categorised as a Write tool in the Things App 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? +

Register the Things App 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 Things App MCP. Nothing to install.

What risk level is update-project? +

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

Can I rate-limit update-project? +

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.

How do I block update-project completely? +

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.

What MCP server provides update-project? +

update-project is provided by the Things App MCP server (lucas-flatwhite/things-app-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

update-project is one line of Things App's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →