Atualiza os metadados de um anexo.
AI agents use atualizar_anexo 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.
This tool modifies metadata of an attachment reversibly—a classic Write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or read-only retrieve data (Read). Severity is medium because unintended metadata changes could affect document organization or access control, but the impact is contained to a single attachment's metadata and reversible.
From the tool's definition Tool name 'atualizar_anexo' (update attachment) and description 'Atualiza os metadados de um anexo' (Updates the metadata of an attachment) indicate a modification operation on existing data.
Attacks that exploit this kind of access
Atualiza os metadados de um anexo. 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 atualizar_anexo: 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.
atualizar_anexo 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 atualizar_anexo 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 atualizar_anexo. 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.
atualizar_anexo 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 →