resources_import_variables
Run resources.import-variables through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-import-variables.md
What resources_import_variables does on Appaloft
AI agents use resources_import_variables to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes | |
exposure | string | Yes | |
plainKeys | array | — | |
resourceId | string | Yes | |
secretKeys | array | — |
Parameters from the server's own tool schema.
Why resources_import_variables is rated Medium
The 'import' operation typically creates or modifies data (variables/resources) in a reversible manner. Without seeing the full schema or knowing if this can overwrite existing variables destructively, this is classified as Write rather than Destructive. The medium severity reflects that importing variables could affect application behavior but is not inherently financial or permanently destructive.
From the tool's definition Tool name contains 'import' and description indicates it 'Run[s] resources.import-variables' which suggests loading and modifying resource variables within the application.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs resources_import_variables safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resources_import_variables, this is the rule to start with:
resources_import_variables 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 Appaloft, apply this rule, and every resources_import_variables call is checked against it from then on.
Questions about resources_import_variables
Run resources.import-variables through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
resources_import_variables accepts 5 parameters: content, exposure, plainKeys, resourceId, secretKeys. Required: content, exposure, resourceId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for resources_import_variables: 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 Appaloft. Nothing to install.
resources_import_variables 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 resources_import_variables 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 resources_import_variables. 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.
resources_import_variables is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue