wf_update_post

Edit an existing post by ID. Rate-limited: 20/hour.

SERVERCrow SOURCEkh0pper/crow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/wf-update-post.md

WHAT IT DOES

What wf_update_post does on Crow

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

RISK

Why wf_update_post is rated Medium

The tool modifies data (posts) but does not delete or destroy information, making it Write rather than Destructive. The rate limit (20/hour) and reversible nature of edits support Write classification. Severity is medium because an AI agent could spam edits, deface posts, or modify project information, but the rate limiting and edit-reversibility prevent it from being high severity.

From the tool's definition Tool description states 'Edit an existing post by ID' — a modification operation that changes existing data reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wf_update_post safely

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

wf_update_post Rate-limited

wf_update_post 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": {
    "wf_update_post": {
      "limits": [
        {
          "counter": "wf_update_post_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 Crow, apply this rule, and every wf_update_post call is checked against it from then on.

FAQ

Questions about wf_update_post

What does the wf_update_post tool do? +

Edit an existing post by ID. Rate-limited: 20/hour. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wf_update_post? +

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

What risk level is wf_update_post? +

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

Can I rate-limit wf_update_post? +

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

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

wf_update_post is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_post_blackboard on Team Manager MCP → The MCP Attack Database →

Guides

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