mw_activate_platform
Activate an additional platform's tool set without restarting the meta-server. Use this when the user adds credentials or asks about a platform that wasn't loaded at boot. After activation, the new tools appear in the catalog and become callable. Returns the activation result (success with toolCo...
This record as markdown: /tools/171county-modwrench/mw-activate-platform.md
What mw_activate_platform does on ModWrench MCP Server
AI agents use mw_activate_platform to create or update resources in ModWrench MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ModWrench MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
platform_id | string | Yes | Platform identifier. Idempotent — activating an already-active platform returns alreadyActive: true with no side effects. |
Parameters from the server's own tool schema.
Why mw_activate_platform is rated Medium
An AI agent can call mw_activate_platform faster than any human can review: one bad instruction and it creates or modifies resources in ModWrench MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs mw_activate_platform safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ModWrench MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mw_activate_platform, this is the rule to start with:
mw_activate_platform 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 ModWrench MCP Server, apply this rule, and every mw_activate_platform call is checked against it from then on.
Questions about mw_activate_platform
Activate an additional platform's tool set without restarting the meta-server. Use this when the user adds credentials or asks about a platform that wasn't loaded at boot. After activation, the new tools appear in the catalog and become callable. Returns the activation result (success with toolCount + baseUrl, or failure with reason — usually a missing-credential hint pointing at modwrench auth login <platform>). It is categorised as a Write tool in the ModWrench MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mw_activate_platform accepts 1 parameter: platform_id. Required: platform_id. The full parameter table on this page comes from the server's own tool schema.
Register the ModWrench MCP Server MCP server in PolicyLayer and add a rule for mw_activate_platform: 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 ModWrench MCP Server. Nothing to install.
mw_activate_platform 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 mw_activate_platform 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 mw_activate_platform. 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.
mw_activate_platform is provided by the ModWrench MCP Server MCP server (@modwrench/cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ModWrench MCP Server, and thousands of servers like it.
This server
Across the catalogue