debug_providers
Debug tool that reports provider resolution details
This record as markdown: /tools/frontmcp/debug-providers.md
What debug_providers does on Frontmcp
AI agents call debug_providers to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why debug_providers is rated Low
The tool returns diagnostic information about how providers are resolved within the MCP framework. It has no capability to modify state, execute external operations, or delete data. The 'reports' verb indicates data retrieval only. Typical blast radius if misused by an AI agent is minimal—worst case is information disclosure about internal system architecture, which has low impact.
From the tool's definition Tool name is 'debug_providers' and description states it 'reports provider resolution details' — this is introspection/querying that retrieves debugging information about internal provider state with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs debug_providers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For debug_providers, this is the rule to start with:
debug_providers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every debug_providers call is checked against it from then on.
Questions about debug_providers
Debug tool that reports provider resolution details. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for debug_providers: 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 Frontmcp. Nothing to install.
debug_providers 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 debug_providers 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 debug_providers. 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.
debug_providers is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue