update_post_status · Noleemits Vision Builder MCP

WHAT IT DOES

What update_post_status does on Noleemits Vision Builder MCP

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

WHY IT NEEDS A POLICY

Why update_post_status needs a policy

While the tool can move content to trash, the description emphasizes reversibility ('restore from trash'), placing it in Write rather than Destructive. However, the consequences are substantial: an AI agent could unpublish live pages, hide content from users, or clutter the trash. This warrants high severity.

From the tool's definition Tool description states: 'Change the status of a post or page (e.g. publish a draft, unpublish, move to trash, restore from trash)'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_post_status Rate-limited

update_post_status 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_post_status": {
      "limits": [
        {
          "counter": "update_post_status_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 Noleemits Vision Builder MCP, so you can run agents against it safely.

FAQ

Questions about update_post_status

What does the update_post_status tool do? +

Change the status of a post or page (e.g. publish a draft, unpublish, move to trash, restore from trash). Shows old and new status. It is categorised as a Write tool in the Noleemits Vision Builder 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_post_status? +

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

What risk level is update_post_status? +

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

Can I rate-limit update_post_status? +

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

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

update_post_status is provided by the Noleemits Vision Builder MCP server (noleemits/vision-builder-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.