AI agents invoke imageMasking to trigger actions in Runware MCP Server. 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.
The description is empty, so classification is based on the tool name and server context. 'imageMasking' likely applies a mask to an image or generates a mask, which is an image transformation/processing operation. Given sibling tools like imageBackgroundRemoval and imageUpscale that execute image processing pipelines via the Runware API, this tool most likely executes an image masking operation.
From the tool's definition Tool name 'imageMasking' on a server that performs image inference, background removal, upscaling, and other image processing operations.
Documented attack patterns abuse exactly the kind of access imageMasking gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Runware MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for imageMasking:
{
"version": "1",
"default": "deny",
"tools": {
"imageMasking": {
"limits": [
{
"counter": "imagemasking_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}imageMasking 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.
imageMasking. It is categorised as a Execute tool in the Runware MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Runware MCP Server MCP server in PolicyLayer and add a rule for imageMasking: 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 Runware MCP Server. Nothing to install.
imageMasking 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 imageMasking 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 imageMasking. 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.
imageMasking is provided by the Runware MCP Server MCP server (runware/mcp-runware). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Runware MCP Server, 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.
11 Runware MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.