project_update

Revision-safely edit project context. Supply expected_revision from project_get and a new request_id. Stale edits conflict instead of overwriting another agent.

SERVERMeta Council SOURCEhttps://meta-council.com/mcp

Medium RISK CLASS

Category Write

Parameters 83 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-meta-council-decision-intelligence/project-update.md

WHAT IT DOES

What project_update does on Meta Council

AI agents use project_update to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.

Parameter	Type	Required
`name`	string	—
`goals`	string	—
`summary`	string	—
`project_id`	string	Yes
`request_id`	string	Yes
`context_kind`	string	—
`repository_url`	string	—
`expected_revision`	integer	Yes

Parameters from the server's own tool schema.

RISK

Why project_update is rated Medium

An AI agent can call project_update faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs project_update safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_update, this is the rule to start with:

project_update Rate-limited

project_update 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": {
    "project_update": {
      "limits": [
        {
          "counter": "project_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every project_update call is checked against it from then on.

FAQ

Questions about project_update

What does the project_update tool do? +

Revision-safely edit project context. Supply expected_revision from project_get and a new request_id. Stale edits conflict instead of overwriting another agent. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does project_update accept? +

project_update accepts 8 parameters: name, goals, summary, project_id, request_id, context_kind, repository_url, expected_revision. Required: project_id, request_id, expected_revision. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on project_update? +

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

What risk level is project_update? +

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

Can I rate-limit project_update? +

Yes. Add a rate_limit block to the project_update 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 project_update completely? +

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

project_update is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Council, and thousands of servers like it.

This server

All 280 Meta Council tools →

Across the catalogue

create_project on Stitch MCP Server →aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →