error_summary

What is RECURRING in the platform error log, rather than what happened last — ask this before list_errors when the question is \

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/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/io-github-proagentstore-platform/error-summary.md

WHAT IT DOES

What error_summary does on ProAgentStore

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

RISK

Why error_summary is rated Low

Tool retrieves and analyzes error log data without side effects or modifications.

From the tool's definition recurring platform error log; query-only, no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs error_summary safely

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

error_summary Allowed

error_summary 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": {
    "error_summary": {}
  }
}

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

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

FAQ

Questions about error_summary

What does the error_summary tool do? +

What is RECURRING in the platform error log, rather than what happened last — ask this before list_errors when the question is \. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on error_summary? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for error_summary: 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 ProAgentStore. Nothing to install.

What risk level is error_summary? +

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

Can I rate-limit error_summary? +

Yes. Add a rate_limit block to the error_summary 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 error_summary completely? +

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

error_summary is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

get_summary on ACE-MCP → The MCP Attack Database →

Guides

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