AI agents call get_session_info to retrieve information from Turtlestack Lite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves session information without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, presenting minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_session_info' and description 'Get information about your current session' indicate data retrieval with no side effects. This is a query operation that returns session metadata.
Documented attack patterns abuse exactly the kind of access get_session_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Turtlestack Lite, and nothing reaches the server without passing your rules. This is the rule we recommend for get_session_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_session_info": {}
}
}get_session_info 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 information about your current session. It is categorised as a Read tool in the Turtlestack Lite MCP Server, which means it retrieves data without modifying state.
Register the Turtlestack Lite MCP server in PolicyLayer and add a rule for get_session_info: 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 Turtlestack Lite. Nothing to install.
get_session_info 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_info 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_info. 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_info is provided by the Turtlestack Lite MCP server (turtlehq-tech/turtlestack-lite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Turtlestack Lite, 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.
45 Turtlestack Lite tools catalogued and risk-classified — across an index of 43,000+ MCP servers.