console_get_logs

Retrieve captured console logs with type and time filters.

SERVERJshookmcp SOURCE@jshookmcp/jshook

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/io-github-vmoranv-jshookmcp/console-get-logs.md

WHAT IT DOES

What console_get_logs does on Jshookmcp

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

RISK

Why console_get_logs is rated Low

Tool retrieves historical logs without side effects or data modification capabilities.

From the tool's definition Retrieve captured console logs with type and time filters.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs console_get_logs safely

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

console_get_logs Allowed

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

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

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

FAQ

Questions about console_get_logs

What does the console_get_logs tool do? +

Retrieve captured console logs with type and time filters. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on console_get_logs? +

Register the Jshook MCP server in PolicyLayer and add a rule for console_get_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 Jshookmcp. Nothing to install.

What risk level is console_get_logs? +

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

Can I rate-limit console_get_logs? +

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

Set action: deny in the PolicyLayer policy for console_get_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 console_get_logs? +

console_get_logs is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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