Fetch a single message by message_id. Use full=true to retrieve the complete stored text
AI agents call get_message to retrieve information from Lore without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves stored message data by identifier. It has no write, execute, or destructive capabilities—it only queries and returns existing data. The blast radius of misuse is minimal; an agent could retrieve unintended messages but cannot modify, delete, or execute operations. This is a straightforward Read operation with low severity.
From the tool's definition Tool name 'get_message' and description 'Fetch a single message by message_id' indicates a retrieval operation with no modification capability.
Documented attack patterns abuse exactly the kind of access get_message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lore, and nothing reaches the server without passing your rules. This is the rule we recommend for get_message:
{
"version": "1",
"default": "deny",
"tools": {
"get_message": {}
}
}get_message 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.
Fetch a single message by message_id. Use full=true to retrieve the complete stored text. It is categorised as a Read tool in the Lore MCP Server, which means it retrieves data without modifying state.
Register the Lore MCP server in PolicyLayer and add a rule for get_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 Lore. Nothing to install.
get_message 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_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 get_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.
get_message is provided by the Lore MCP server (jordanhindo/lore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lore, 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.
8 Lore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.