Get comprehensive context for a project: recent sessions, key topics, common tools, and patterns. Useful for session-start context injection.
AI agents call get_project_context to retrieve information from ClaudeHistoryMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates historical project information (sessions, topics, tools, patterns) for contextual awareness. It performs no side effects, does not modify state, execute code, delete data, or involve financial operations. It is a straightforward Read operation that queries indexed history to support session initialization.
From the tool's definition Tool name 'get_project_context' and description stating it 'Get[s] comprehensive context for a project: recent sessions, key topics, common tools, and patterns' indicates pure data retrieval with no modifications, deletions, or external operations.
Documented attack patterns abuse exactly the kind of access get_project_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ClaudeHistoryMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_project_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_project_context": {}
}
}get_project_context 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 comprehensive context for a project: recent sessions, key topics, common tools, and patterns. Useful for session-start context injection. It is categorised as a Read tool in the ClaudeHistoryMCP MCP Server, which means it retrieves data without modifying state.
Register the ClaudeHistory MCP server in PolicyLayer and add a rule for get_project_context: 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 ClaudeHistoryMCP. Nothing to install.
get_project_context 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_project_context 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_project_context. 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_project_context is provided by the ClaudeHistory MCP server (jhammant/claudehistorymcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ClaudeHistoryMCP, 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.
9 ClaudeHistoryMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.