Publica um comando de scaling (scale up/down/restart) de workers.
AI agents invoke aplicar_scaling to trigger actions in MCP Officegest. 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 external operations that control worker infrastructure. Scaling operations can disrupt service availability, cause downtime, or trigger resource reallocation with immediate effects. While not financial or destructive of data, the blast radius is significant: an AI agent invoking this carelessly could scale down production workers, causing outages.
From the tool's definition 'Publica um comando de scaling (scale up/down/restart) de workers' – directly triggers infrastructure operations (scale up, scale down, restart) on worker processes.
Attacks that exploit this kind of access
Publica um comando de scaling (scale up/down/restart) de workers. It is categorised as a Execute tool in the MCP Officegest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for aplicar_scaling: 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 Officegest. Nothing to install.
aplicar_scaling 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 aplicar_scaling 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 aplicar_scaling. 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.
aplicar_scaling is provided by the MCP Officegest MCP server (rubencodex86/officegest-api-v2-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →