This record as markdown: /tools/delimit/delimit-session-history.md
What delimit_session_history does on Delimit
AI agents call delimit_session_history to retrieve information from Delimit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why delimit_session_history is rated Low
The tool appears designed to query or fetch session history records within the Delimit workspace platform. No description is provided, which lowers confidence slightly, but the name strongly suggests this is a read-only operation to access historical data rather than modify, execute operations, or delete records. Historical data retrieval has minimal blast radius if misused by an agent.
From the tool's definition Tool name 'delimit_session_history' suggests retrieval of historical session data. The empty description limits certainty, but the naming convention (past tense 'history') and context of a workspace management tool indicate this is a data retrieval operation…
Attacks that exploit this kind of access
The rule that runs delimit_session_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delimit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delimit_session_history, this is the rule to start with:
delimit_session_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delimit, apply this rule, and every delimit_session_history call is checked against it from then on.
Questions about delimit_session_history
delimit_session_history is a read tool on the Delimit MCP server. It is categorised as a Read tool in the Delimit MCP Server, which means it retrieves data without modifying state.
Register the Delimit MCP server in PolicyLayer and add a rule for delimit_session_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 Delimit. Nothing to install.
delimit_session_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 delimit_session_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 delimit_session_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.
delimit_session_history is provided by the Delimit MCP server (delimit-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delimit, and thousands of servers like it.
This server
Across the catalogue