associar_contacto
AI agents use associar_contacto 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 name indicates a reversible data modification action (associating/linking a contact), consistent with Write category (create/modify data). It appears to be part of a CRM/business management system managing client relationships. Without a description confirming scope (e.g., whether it can delete associations or modify sensitive contact fields), severity is medium.
From the tool's definition Tool name 'associar_contacto' (associate contact) suggests linking/associating a contact record. Follows the naming pattern of other CRUD tools on this Officegest server (atualizar_*, adicionar_*, etc.) which manage clients and operational data.
Attacks that exploit this kind of access
associar_contacto. 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 associar_contacto: 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.
associar_contacto 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 associar_contacto 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 associar_contacto. 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.
associar_contacto 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 →