Send a message to the current conversation
AI agents use send_kogna_message to create or update resources in Kogna MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kogna MCP Server environment.
Sending a message writes new data to the conversation state. It is reversible in principle (conversation history could be cleared) but is a creation/modification action. It does not execute code, delete data, or involve finances. Severity is medium because messages sent to an AI avatar system could trigger unintended agent actions depending on downstream processing.
From the tool's definition 'Send a message to the current conversation' — creates a new message entry in an ongoing conversation
Attacks that exploit this kind of access
Send a message to the current conversation. It is categorised as a Write tool in the Kogna MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kogna MCP Server MCP server in PolicyLayer and add a rule for send_kogna_message: 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 Kogna MCP Server. Nothing to install.
send_kogna_message 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 send_kogna_message 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 send_kogna_message. 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.
send_kogna_message is provided by the Kogna MCP Server MCP server (subbu3012/kognamcp). 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 →