Import a verified portable archive into a new local Run402 Core project through the Core gateway. Automatically verifies before import, supports dry_run and require_runnable, and reports SECRET_VALUES_REQUIRED with next actions.
AI agents use import_project_archive to create or update resources in Run402 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Run402 environment.
The import operation creates a new project and modifies the infrastructure state, making it a Write action rather than Read. The severity is high because: (1) it creates new computational infrastructure/projects, (2) it processes and imports archives which could contain malicious configurations, (3) it requires secret values handling which could lead to credential exposure if misused.
From the tool's definition Tool name and description indicate the ability to import a project archive into a new local project, which creates or modifies infrastructure and project state.
Attacks that exploit this kind of access
Import a verified portable archive into a new local Run402 Core project through the Core gateway. Automatically verifies before import, supports dry_run and require_runnable, and reports SECRET_VALUES_REQUIRED with next actions. It is categorised as a Write tool in the Run402 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Run402 MCP server in PolicyLayer and add a rule for import_project_archive: 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 Run402. Nothing to install.
import_project_archive 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 import_project_archive 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 import_project_archive. 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.
import_project_archive is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →