bug-status

Check if the OAuth bug has been reproduced

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/bug-status.md

WHAT IT DOES

What bug-status does on Mcp Test Servers

AI agents call bug-status 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 bug-status is rated Low

This tool retrieves bug status information without modifying, deleting, or executing external operations. It is a simple lookup/query operation, fitting the Read category. The severity is low because checking a bug status has minimal blast radius even if misused by an AI agent—it cannot directly harm systems or data.

From the tool's definition The tool 'bug-status' is described as 'Check if the OAuth bug has been reproduced', which queries or checks the status of a bug—a read-only information retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bug-status 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 bug-status, this is the rule to start with:

bug-status Allowed

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

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 bug-status call is checked against it from then on.

FAQ

Questions about bug-status

What does the bug-status tool do? +

Check if the OAuth bug has been reproduced. 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 bug-status? +

Register the Mcp Test Servers MCP server in PolicyLayer and add a rule for bug-status: 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 bug-status? +

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

Can I rate-limit bug-status? +

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

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

bug-status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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