get_console_logs

取得 Console 記錄（warn/error）。Console logs.

SERVERBugEzy SOURCEhttps://bugezy.dev/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-bugezy-bugezy/get-console-logs.md

WHAT IT DOES

What get_console_logs does on BugEzy

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

Parameter	Type	Required	Description
`report_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_console_logs is rated Low

Even though get_console_logs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_console_logs safely

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

get_console_logs Allowed

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

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

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

FAQ

Questions about get_console_logs

What does the get_console_logs tool do? +

取得 Console 記錄（warn/error）。Console logs. It is categorised as a Read tool in the BugEzy MCP Server, which means it retrieves data without modifying state.

What parameters does get_console_logs accept? +

get_console_logs accepts 1 parameter: report_id. Required: report_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_console_logs? +

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

What risk level is get_console_logs? +

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

Can I rate-limit get_console_logs? +

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

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

get_console_logs is provided by the BugEzy MCP server (https://bugezy.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on BugEzy, and thousands of servers like it.

This server

All 13 BugEzy tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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