office_create_manifest
Create a basic Office Add-in manifest template
This record as markdown: /tools/mukul975-mcp-windows-automation/office-create-manifest.md
What office_create_manifest does on Mcp Windows
AI agents use office_create_manifest to create or update resources in Mcp Windows, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Windows environment.
Why office_create_manifest is rated Medium
This tool creates a new manifest file artifact for Office Add-ins, which is a reversible write operation. It does not execute code, delete data, or move money. The severity is medium because a maliciously crafted manifest could potentially be used to load malicious Office Add-ins or modify Office behavior, but the tool itself only generates a template—actual deployment and execution depend on subsequent actions.
From the tool's definition Tool name 'office_create_manifest' and description 'Create a basic Office Add-in manifest template' indicate file creation (manifest template generation). The verb 'Create' and action of generating a new artifact classify this as a Write operation.
Attacks that exploit this kind of access
The rule that runs office_create_manifest safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For office_create_manifest, this is the rule to start with:
office_create_manifest 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 Mcp Windows, apply this rule, and every office_create_manifest call is checked against it from then on.
Questions about office_create_manifest
Create a basic Office Add-in manifest template. It is categorised as a Write tool in the Mcp Windows MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for office_create_manifest: 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 Mcp Windows. Nothing to install.
office_create_manifest 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 office_create_manifest 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 office_create_manifest. 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.
office_create_manifest is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Windows, and thousands of servers like it.
This server
Across the catalogue