AI agents call view_session_history to retrieve information from Guru Pk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries historical session information. It performs no side effects—no data is created, modified, deleted, or executed. The function is purely informational, consistent with the Read category. Given it accesses only session history metadata within a debate/discussion context, the severity is low.
From the tool's definition Tool name 'view_session_history' and description '查看会话历史' (view session history) indicate retrieval of existing session data without modification.
Documented attack patterns abuse exactly the kind of access view_session_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Guru Pk, and nothing reaches the server without passing your rules. This is the rule we recommend for view_session_history:
{
"version": "1",
"default": "deny",
"tools": {
"view_session_history": {}
}
}view_session_history 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.
查看会话历史. It is categorised as a Read tool in the Guru Pk MCP Server, which means it retrieves data without modifying state.
Register the Guru Pk MCP server in PolicyLayer and add a rule for view_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 Guru Pk. Nothing to install.
view_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 view_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 view_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.
view_session_history is provided by the Guru Pk MCP server (mitsudoai/guru-pk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Guru Pk, 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.
22 Guru Pk tools catalogued and risk-classified — across an index of 43,000+ MCP servers.