adaptercloud_policies_update
Update a governance policy. At least one mutable field must be provided. Use isActive to enable/disable a policy.
This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-policies-update.md
What adaptercloud_policies_update does on Adaptercloud
AI agents use adaptercloud_policies_update to create or update resources in Adaptercloud, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adaptercloud environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Policy ID |
kind | string | — | Updated policy kind |
name | string | — | Updated name |
tags | array | — | Updated tags |
isActive | boolean | — | Updated active flag |
severity | string | — | Updated severity |
appliesTo | array | — | Updated resource-type selectors |
expression | object | — | Updated policy-rule expression JSON |
description | string | — | Updated description |
enforcement | string | — | Updated enforcement mode |
Parameters from the server's own tool schema.
Why adaptercloud_policies_update is rated Medium
An AI agent can call adaptercloud_policies_update faster than any human can review: one bad instruction and it creates or modifies resources in Adaptercloud by the hundred, each call as confident as the last.
Risk signalsAccepts freeform code/query input (expression) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs adaptercloud_policies_update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adaptercloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adaptercloud_policies_update, this is the rule to start with:
adaptercloud_policies_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Adaptercloud, apply this rule, and every adaptercloud_policies_update call is checked against it from then on.
Questions about adaptercloud_policies_update
Update a governance policy. At least one mutable field must be provided. Use isActive to enable/disable a policy. It is categorised as a Write tool in the Adaptercloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
adaptercloud_policies_update accepts 10 parameters: id, kind, name, tags, isActive, severity, appliesTo, expression, description, enforcement. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_policies_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 Adaptercloud. Nothing to install.
adaptercloud_policies_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adaptercloud_policies_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.
Set action: deny in the PolicyLayer policy for adaptercloud_policies_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.
adaptercloud_policies_update is provided by the Adaptercloud MCP server (@burdenoff/adaptercloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adaptercloud, and thousands of servers like it.
This server
Across the catalogue