canvas_pick_object_at_point

Pick / hit-test the topmost object at a given screen coordinate using the engine

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/canvas-pick-object-at-point.md

WHAT IT DOES

What canvas_pick_object_at_point does on Jshookmcp

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

Tool queries canvas state to identify objects at coordinates; no side effects.

From the tool's definition Pick / hit-test the topmost object at a given screen coordinate

Attacks that exploit this kind of access

RECOMMENDED RULE

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

canvas_pick_object_at_point Allowed

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

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

FAQ

Questions about canvas_pick_object_at_point

What does the canvas_pick_object_at_point tool do? +

Pick / hit-test the topmost object at a given screen coordinate using the engine. 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 canvas_pick_object_at_point? +

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

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

Can I rate-limit canvas_pick_object_at_point? +

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

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

canvas_pick_object_at_point 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

The MCP Attack Database →

Guides

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