List all console messages for the currently selected page since the last navigation.
AI agents call list_console_messages 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.
This tool retrieves historical console output data from the browser's debugging interface. It performs a query operation on already-captured logging data without modifying state, triggering code execution, or affecting system resources. The blast radius of misuse is minimal—an agent could only read what has already been logged, which is informational data. This fits cleanly into the Read category.
From the tool's definition Tool name is 'list_console_messages' and description states it 'List[s] all console messages' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_console_messages gives an agent:
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 list_console_messages:
{
"version": "1",
"default": "deny",
"tools": {
"list_console_messages": {}
}
} list_console_messages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all console messages for the currently selected page since the last navigation. It is categorised as a Read tool in the ReverseCraft DevTools MCP MCP Server, which means it retrieves data without modifying state.
Register the ReverseCraft DevTools MCP server in PolicyLayer and add a rule for list_console_messages: 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.
list_console_messages 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 list_console_messages 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 list_console_messages. 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.
list_console_messages 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.
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.