debug-oauth

Returns OAuth debugging information

SERVERMcp Test Servers SOURCEmsfeldstein/mcp-test-servers

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-test-servers/debug-oauth.md

WHAT IT DOES

What debug-oauth does on Mcp Test Servers

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

RISK

Why debug-oauth is rated Low

This tool retrieves debugging information about OAuth configurations. While it does not modify data (Read category), OAuth debug information can contain sensitive details like client IDs, redirect URIs, or other configuration that could be misused if exposed.

From the tool's definition Tool name 'debug-oauth' and description 'Returns OAuth debugging information' indicate retrieval of OAuth configuration/state data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs debug-oauth safely

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

debug-oauth Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Test Servers, apply this rule, and every debug-oauth call is checked against it from then on.

FAQ

Questions about debug-oauth

What does the debug-oauth tool do? +

Returns OAuth debugging information. It is categorised as a Read tool in the Mcp Test Servers MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on debug-oauth? +

Register the Mcp Test Servers MCP server in PolicyLayer and add a rule for debug-oauth: 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 Test Servers. Nothing to install.

What risk level is debug-oauth? +

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

Can I rate-limit debug-oauth? +

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

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

debug-oauth is provided by the Mcp Test Servers MCP server (msfeldstein/mcp-test-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Test Servers, and thousands of servers like it.

This server

All 67 Mcp Test Servers tools →

Across the catalogue

The MCP Attack Database →

Guides

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