AI agents invoke chat to trigger actions in WeKnora MCP Server. 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.
Sending a chat message triggers an external operation against a session in the WeKnora API. It is not a pure read (it has side effects by creating a message/interaction in the session), nor is it a write of data that can be simply reversed.
From the tool's definition Send a chat message to a session
Documented attack patterns abuse exactly the kind of access chat gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WeKnora MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for chat:
{
"version": "1",
"default": "deny",
"tools": {
"chat": {
"limits": [
{
"counter": "chat_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}chat stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Send a chat message to a session. It is categorised as a Execute tool in the WeKnora MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WeKnora MCP Server MCP server in PolicyLayer and add a rule for chat: 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 WeKnora MCP Server. Nothing to install.
chat 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 chat 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 chat. 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.
chat is provided by the WeKnora MCP Server MCP server (nannaolympicbroadcast/weknoramcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WeKnora MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 WeKnora MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.