New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

history_get

获取某次协作的详细记录

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-get.md

What history_get does on Claude Team MCP

AI agents call history_get 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.

Why history_get is rated Low

This tool retrieves and reads historical collaboration records. It performs a query operation to fetch existing data about past interactions between AI models. There is no indication of data modification, deletion, execution of code, or financial impact. The action is read-only and informational, making it a Read category tool with low severity.

From the tool's definition Tool name 'history_get' and description '获取某次协作的详细记录' (Get detailed records of a collaboration session) indicate retrieval of historical data without modification or side effects.

Questions about history_get

What does the history_get 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_get? +

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

What risk level is history_get? +

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

Can I rate-limit history_get? +

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

How do I block history_get completely? +

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

What MCP server provides history_get? +

history_get 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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Team's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.