get_error_history

获取错误历史记录,可以查看最近的错误趋势和模式。

Server MCP Sentry Analyzer ranruan/mcp
Category Read
Risk class Low
Parameters 00 required

What get_error_history does on MCP Sentry Analyzer

AI agents call get_error_history to retrieve information from MCP Sentry Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_error_history needs a policy

This tool retrieves historical error data from Sentry for analysis purposes. It performs a read-only query operation that accesses existing error records to identify trends and patterns. There are no side effects, no data modification, no code execution, and no destructive operations.

From the tool's definition Tool name 'get_error_history' and description '获取错误历史记录,可以查看最近的错误趋势和模式' (Get error history records, view recent error trends and patterns) indicate data retrieval with no modification or execution capability.

Questions about get_error_history

What does the get_error_history tool do? +

获取错误历史记录,可以查看最近的错误趋势和模式。. It is categorised as a Read tool in the MCP Sentry Analyzer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_error_history? +

Register the MCP Sentry Analyzer MCP server in PolicyLayer and add a rule for get_error_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 MCP Sentry Analyzer. Nothing to install.

What risk level is get_error_history? +

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

Can I rate-limit get_error_history? +

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

How do I block get_error_history completely? +

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

What MCP server provides get_error_history? +

get_error_history is provided by the MCP Sentry Analyzer MCP server (ranruan/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.