Comunica um documento de transporte ao webservice da AT (Autoridade Tributária).
AI agents invoke comunicar_documento_at 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 triggers an external operation by submitting/communicating a transport document to the Portuguese Tax Authority (AT) web service. It initiates an external API call to a government system, which constitutes executing an external operation with real-world regulatory and legal implications. The effect depends on the document being submitted and cannot trivially be undone once communicated to the tax authority.
From the tool's definition Comunica um documento de transporte ao webservice da AT (Autoridade Tributária)
Attacks that exploit this kind of access
Comunica um documento de transporte ao webservice da AT (Autoridade Tributária). 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 comunicar_documento_at: 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.
comunicar_documento_at 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 comunicar_documento_at 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 comunicar_documento_at. 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.
comunicar_documento_at 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 →