Launch an new microsoft excel application or use the existed one.
AI agents invoke Launch to trigger actions in OfficeMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an external operation (application launch) whose effects depend on arguments and system context. While launching Excel itself is not inherently destructive, it enables subsequent Execute operations on Office documents and data through the OfficeMCP server's automation capabilities.
From the tool's definition Tool 'Launch' invokes Microsoft Excel application startup or retrieval through COM interface on Windows. The description states it will 'Launch an new microsoft excel application or use the existed one', which represents triggering an external application…
Documented attack patterns abuse exactly the kind of access Launch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OfficeMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for Launch:
{
"version": "1",
"default": "deny",
"tools": {
"Launch": {
"limits": [
{
"counter": "launch_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}Launch stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Launch an new microsoft excel application or use the existed one. It is categorised as a Execute tool in the OfficeMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Office MCP server in PolicyLayer and add a rule for Launch: 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 OfficeMCP. Nothing to install.
Launch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the Launch 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 Launch. 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.
Launch is provided by the Office MCP server (officemcp/officemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 OfficeMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 OfficeMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.