Medium Risk

click_at

Clicks at the provided coordinates.

Part of the Safari DevTools MCP server.

click_at can modify Safari DevTools MCP data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SAFARI DEVTOOLS MCP →

Free to start. No card required.

AI agents use click_at to create or modify resources in Safari DevTools MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call click_at repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Safari DevTools MCP.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "click_at": {
      "limits": [
        {
          "counter": "click_at_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Safari DevTools MCP policy for all 53 tools.

Get this rule live on your own Safari DevTools MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SAFARI DEVTOOLS MCP →

View all 53 tools →

These attack patterns abuse exactly the kind of access click_at gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so click_at only ever does what you allow.

SECURE SAFARI DEVTOOLS MCP →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the click_at tool do? +

Clicks at the provided coordinates.. It is categorised as a Write tool in the Safari DevTools MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on click_at? +

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

What risk level is click_at? +

click_at is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit click_at? +

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

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

click_at is provided by the Safari DevTools MCP server (safari-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 Safari DevTools MCP tool call.

Deterministic rules across all 53 Safari DevTools MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.