pine_session_get
Get session details including state, title, and timestamps.
This record as markdown: /tools/19pine-ai-pine-mcp-server/pine-session-get.md
What pine_session_get does on Pine Assistant MCP Server
AI agents call pine_session_get to retrieve information from Pine Assistant MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pine_session_get is rated Low
This tool performs a read-only query to retrieve session information. It has no side effects and does not create, modify, or delete data. The blast radius if misused is minimal—an agent could only obtain information about session state and timestamps, which does not compromise security, enable unauthorized actions, or cause harm.
From the tool's definition Tool description states 'Get session details' which is a retrieval operation. The verb 'Get' indicates data retrieval without modification. Session metadata (state, title, timestamps) are informational attributes.
Attacks that exploit this kind of access
The rule that runs pine_session_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pine Assistant MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pine_session_get, this is the rule to start with:
pine_session_get 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 Pine Assistant MCP Server, apply this rule, and every pine_session_get call is checked against it from then on.
Questions about pine_session_get
Get session details including state, title, and timestamps. It is categorised as a Read tool in the Pine Assistant MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pine Assistant MCP Server MCP server in PolicyLayer and add a rule for pine_session_get: 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 Pine Assistant MCP Server. Nothing to install.
pine_session_get 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 pine_session_get 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 pine_session_get. 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.
pine_session_get is provided by the Pine Assistant MCP Server MCP server (19pine-ai/pine-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pine Assistant MCP Server, and thousands of servers like it.
This server
Across the catalogue