history_context

获取最近的协作上下文，可用于继续之前的工作

SERVERClaude Team MCP SOURCE7836246/claude-team-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/7836246-claude-team-mcp/history-context.md

WHAT IT DOES

What history_context does on Claude Team MCP

AI agents call history_context to retrieve information from Claude Team MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why history_context is rated Low

This tool queries and retrieves historical collaboration data and context to enable users to resume prior work. It has no side effects, creates no new data, executes no code, and performs no destructive or financial operations.

From the tool's definition Tool name 'history_context' with description indicating it 'retrieves/gets recent collaboration context' (获取最近的协作上下文) for continuing previous work.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs history_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Team MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For history_context, this is the rule to start with:

history_context Allowed

history_context is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "history_context": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Team MCP, apply this rule, and every history_context call is checked against it from then on.

FAQ

Questions about history_context

What does the history_context tool do? +

获取最近的协作上下文，可用于继续之前的工作. It is categorised as a Read tool in the Claude Team MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on history_context? +

Register the Claude Team MCP server in PolicyLayer and add a rule for history_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 Claude Team MCP. Nothing to install.

What risk level is history_context? +

history_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit history_context? +

Yes. Add a rate_limit block to the history_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.

How do I block history_context completely? +

Set action: deny in the PolicyLayer policy for history_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.

What MCP server provides history_context? +

history_context is provided by the Claude Team MCP server (7836246/claude-team-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Team, and thousands of servers like it.

This server

All 18 Claude Team tools →

Across the catalogue

editor_context on 010 Editor →search_context on ACE-MCP → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →