Recolhe e guarda um novo snapshot de estatísticas para um período.
AI agents use capturar_snapshot_queue to create or update resources in MCP Officegest — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Officegest environment.
The tool collects and saves (guarda) a new snapshot of statistics, which is a write/create operation. It does not delete or overwrite existing data irreversibly, nor does it execute arbitrary code or involve financial transactions. Severity is medium because writing snapshot data could affect reporting accuracy or storage, but impact is limited.
From the tool's definition 'Recolhe e guarda um novo snapshot' — explicitly creates/saves a new snapshot of statistics for a period
Attacks that exploit this kind of access
Recolhe e guarda um novo snapshot de estatísticas para um período. It is categorised as a Write tool in the MCP Officegest MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Officegest MCP server in PolicyLayer and add a rule for capturar_snapshot_queue: 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.
capturar_snapshot_queue 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 capturar_snapshot_queue 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 capturar_snapshot_queue. 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.
capturar_snapshot_queue 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 →