install_product
Agent-native install after demo/founding: returns paste_this (system_prompt_short) + export URLs + loop tick recipe. No browser. Pass access_token from demo or founding_free.
This record as markdown: /tools/dev-dualregistry-registry/install-product.md
What install_product does on Dual Registry
AI agents use install_product to create or update resources in Dual Registry, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dual Registry environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
token | string | — | Alias for access_token |
order_id | string | — | |
access_token | string | — |
Parameters from the server's own tool schema.
Why install_product is rated Medium
An AI agent can call install_product faster than any human can review: one bad instruction and it creates or modifies resources in Dual Registry by the hundred, each call as confident as the last.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs install_product safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dual Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For install_product, this is the rule to start with:
install_product 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 Dual Registry, apply this rule, and every install_product call is checked against it from then on.
Questions about install_product
Agent-native install after demo/founding: returns paste_this (system_prompt_short) + export URLs + loop tick recipe. No browser. Pass access_token from demo or founding_free. It is categorised as a Write tool in the Dual Registry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
install_product accepts 3 parameters: token, order_id, access_token. The full parameter table on this page comes from the server's own tool schema.
Register the Dual Registry MCP server in PolicyLayer and add a rule for install_product: 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 Dual Registry. Nothing to install.
install_product 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 install_product 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 install_product. 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.
install_product is provided by the Dual Registry MCP server (https://www.dualregistry.dev/api/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dual Registry, and thousands of servers like it.
This server
Across the catalogue