Low Risk

get_console_message

Gets a console message by its ID. You can get all messages by calling ${listConsoleMessages.name}.

How to control get_console_message ↓

What get_console_message does on ReverseCraft DevTools MCP

AI agents call get_console_message to retrieve information from ReverseCraft DevTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_console_message needs a policy

This tool retrieves existing console messages by identifier—a pure read operation with no side effects. While the broader server enables browser automation and potential abuse, this specific tool simply queries historical console data. Severity is low because console messages contain debug information rather than sensitive user data or credentials, and retrieval alone poses minimal risk.

From the tool's definition Tool name 'get_console_message' and description 'Gets a console message by its ID' indicate retrieval without modification. The reference to 'calling listConsoleMessages' to obtain all messages reinforces read-only behavior.

Documented attack patterns abuse exactly the kind of access get_console_message gives an agent:

How to control get_console_message

PolicyLayer is an MCP gateway — it sits between your AI agents and ReverseCraft DevTools MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_console_message:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_console_message": {}
  }
}

get_console_message is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ReverseCraft DevTools MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_console_message

What does the get_console_message tool do? +

Gets a console message by its ID. You can get all messages by calling ${listConsoleMessages.name}. It is categorised as a Read tool in the ReverseCraft DevTools MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_console_message? +

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

What risk level is get_console_message? +

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

Can I rate-limit get_console_message? +

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

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

get_console_message is provided by the ReverseCraft DevTools MCP server (reverse-craft/rc-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ReverseCraft DevTools MCP tool call.

Start from ReverseCraft DevTools MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

46 ReverseCraft DevTools MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.