create_agent_chat_event
AI agents use create_agent_chat_event to create or update resources in Thenvoi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Thenvoi MCP Server environment.
The tool appears to create chat events based on naming conventions and the server's stated capability to 'post execution events'. This is a Write operation (creates data reversibly). Severity is medium because event creation in a chat platform could have side effects on other agents/users, but lacks the irreversibility of Destructive or financial impact.
From the tool's definition Tool name 'create_agent_chat_event' suggests creating/posting events; server description mentions 'post execution events' which aligns with Write operations. No description provided for this specific tool.
Attacks that exploit this kind of access
create_agent_chat_event. It is categorised as a Write tool in the Thenvoi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Thenvoi MCP Server MCP server in PolicyLayer and add a rule for create_agent_chat_event: 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 Thenvoi MCP Server. Nothing to install.
create_agent_chat_event 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 create_agent_chat_event 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 create_agent_chat_event. 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.
create_agent_chat_event is provided by the Thenvoi MCP Server MCP server (thenvoi/thenvoi-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 →