Remove the background from an image in a document using AI (Creator Studio only).
AI agents invoke pages_remove_background to trigger actions in Iwork. 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 triggers an AI-powered image processing operation on an existing document image. It modifies the document content (background removal is potentially irreversible without undo), but primarily it executes an external AI operation. It falls under Execute as it triggers an external AI processing pipeline.
From the tool's definition Remove the background from an image in a document using AI (Creator Studio only)
Documented attack patterns abuse exactly the kind of access pages_remove_background gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Iwork, and nothing reaches the server without passing your rules. This is the rule we recommend for pages_remove_background:
{
"version": "1",
"default": "deny",
"tools": {
"pages_remove_background": {
"limits": [
{
"counter": "pages_remove_background_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} pages_remove_background 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.
Remove the background from an image in a document using AI (Creator Studio only). It is categorised as a Execute tool in the Iwork MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iwork MCP server in PolicyLayer and add a rule for pages_remove_background: 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 Iwork. Nothing to install.
pages_remove_background 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 pages_remove_background 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 pages_remove_background. 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.
pages_remove_background is provided by the Iwork MCP server (reichenbach/iwork_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Iwork, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
114 Iwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.