adaptercloud_resources_register
Upsert a discovered resource for a connection (idempotent by externalId). Re-registering the same externalId updates the existing resource.
This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-resources-register.md
What adaptercloud_resources_register does on Adaptercloud
AI agents use adaptercloud_resources_register 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 |
|---|---|---|---|
name | string | Yes | Resource display name |
tags | array | — | Workspace-side free-form tags |
region | string | — | Resource region |
attributes | object | — | Provider-native resource attributes JSON |
externalId | string | Yes | Provider-native unique ID (idempotency key) |
monthlyCost | number | — | Estimated monthly cost |
connectionId | string | Yes | Connection the resource was discovered through |
providerTags | object | — | Provider-native tags JSON |
resourceType | string | Yes | Provider resource type, e.g. "aws_instance" |
Parameters from the server's own tool schema.
Why adaptercloud_resources_register is rated Medium
An AI agent can call adaptercloud_resources_register 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.
Attacks that exploit this kind of access
The rule that runs adaptercloud_resources_register 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_resources_register, this is the rule to start with:
adaptercloud_resources_register 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_resources_register call is checked against it from then on.
Questions about adaptercloud_resources_register
Upsert a discovered resource for a connection (idempotent by externalId). Re-registering the same externalId updates the existing resource. 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_resources_register accepts 9 parameters: name, tags, region, attributes, externalId, monthlyCost, connectionId, providerTags, resourceType. Required: name, externalId, connectionId, resourceType. 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_resources_register: 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_resources_register 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_resources_register 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_resources_register. 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_resources_register 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