Return one logical session as a single chronological timeline, folding the primary thread
AI agents call get_session 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 and returns historical session data in a read-only manner. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial operations. The action is purely informational—reconstructing a chronological view of past interactions for recall purposes, which aligns with the 'Read' category for data retrieval operations.
From the tool's definition Tool name 'get_session' and description 'Return one logical session as a single chronological timeline' indicate retrieval and querying of stored session data with no modification, deletion, or external execution.
Documented attack patterns abuse exactly the kind of access get_session 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_session:
{
"version": "1",
"default": "deny",
"tools": {
"get_session": {}
}
}get_session 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.
Return one logical session as a single chronological timeline, folding the primary thread. 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_session: 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_session 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_session 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_session. 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_session 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.