AI agents call get_chat_history to retrieve information from Joinly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical chat data without modifying, deleting, or executing operations. No side effects are implied. The low severity reflects minimal blast radius—chat history access poses limited risk even if misused by an AI agent, though confidence is reduced due to the missing description.
From the tool's definition Tool name 'get_chat_history' indicates retrieval of existing chat messages. The empty description limits direct confirmation, but context from sibling tools (send_chat_message, get_transcript, get_participants) and the tool's naming pattern align with…
Documented attack patterns abuse exactly the kind of access get_chat_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Joinly, and nothing reaches the server without passing your rules. This is the rule we recommend for get_chat_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_chat_history": {}
}
}get_chat_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_chat_history. It is categorised as a Read tool in the Joinly MCP Server, which means it retrieves data without modifying state.
Register the Joinly MCP server in PolicyLayer and add a rule for get_chat_history: 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 Joinly. Nothing to install.
get_chat_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_chat_history 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 get_chat_history. 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.
get_chat_history is provided by the Joinly MCP server (joinly-ai/joinly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Joinly, 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.
12 Joinly tools catalogued and risk-classified — across an index of 43,000+ MCP servers.