AI agents call get_messages to retrieve information from Membase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves existing messages from persistent storage with no modification, deletion, or execution capability. Even if an AI agent misuses this tool, it can only access already-stored messages—a low blast radius. Low confidence reflects the empty description, but the name and server context strongly suggest a read-only operation.
From the tool's definition Tool name 'get_messages' indicates retrieval of stored messages. Server context describes persistent memory storage and retrieval functionality.
Documented attack patterns abuse exactly the kind of access get_messages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Membase MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_messages:
{
"version": "1",
"default": "deny",
"tools": {
"get_messages": {}
}
}get_messages 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_messages. It is categorised as a Read tool in the Membase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Membase MCP Server MCP server in PolicyLayer and add a rule for get_messages: 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 Membase MCP Server. Nothing to install.
get_messages 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_messages 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_messages. 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_messages is provided by the Membase MCP Server MCP server (unibaseio/membase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Membase 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.
4 Membase MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.