estado_scaling
Estado de scaling de uma fila (ou todas num vhost): contagem de workers,
This record as markdown: /tools/rubencodex86-officegest-api-v2-mcp/estado-scaling.md
What estado_scaling does on MCP Officegest
AI agents call estado_scaling to retrieve information from MCP Officegest without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why estado_scaling is rated Low
The tool retrieves status information (worker counts, scaling state) for a queue or all queues in a vhost. This is a read-only monitoring/query operation with no side effects. Low severity as it only exposes operational metrics.
From the tool's definition 'Estado de scaling de uma fila' — 'estado' means 'state/status', indicating a read/query operation that retrieves worker count and scaling status of a queue
Attacks that exploit this kind of access
The rule that runs estado_scaling safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Officegest, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For estado_scaling, this is the rule to start with:
estado_scaling is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Officegest, apply this rule, and every estado_scaling call is checked against it from then on.
Questions about estado_scaling
Estado de scaling de uma fila (ou todas num vhost): contagem de workers,. It is categorised as a Read tool in the MCP Officegest MCP Server, which means it retrieves data without modifying state.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for estado_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.
estado_scaling is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the estado_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 estado_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.
estado_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.
More on MCP Officegest, and thousands of servers like it.
This server
Across the catalogue