skia_detect_renderer

Detect the active Skia renderer backend from the current page context.

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/skia-detect-renderer.md

WHAT IT DOES

What skia_detect_renderer does on Jshookmcp

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

This tool retrieves renderer information from the page without modifying state, executing arbitrary code, deleting data, or moving money. It is a passive inspection/query operation, placing it squarely in the Read category. Severity is low because detecting a renderer backend poses minimal risk even if misused by an agent.

From the tool's definition The tool 'skia_detect_renderer' detects (queries/inspects) the active Skia renderer backend from the current page context. The verb 'detect' combined with 'from the current page context' indicates information retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

skia_detect_renderer Allowed

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

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

FAQ

Questions about skia_detect_renderer

What does the skia_detect_renderer tool do? +

Detect the active Skia renderer backend from the current page context. 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 skia_detect_renderer? +

Register the Jshook MCP server in PolicyLayer and add a rule for skia_detect_renderer: 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 skia_detect_renderer? +

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

Can I rate-limit skia_detect_renderer? +

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

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

skia_detect_renderer 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

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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