puppeteer_get_element_info

THE RISK

Low Risk

Why puppeteer_get_element_info needs a policy

This is a read-only operation that queries element properties in a browser context. It has no side effects, does not modify data, execute code, delete resources, or affect financial systems. The tool merely inspects and returns element details, making it a classic Read category tool with low severity impact.

From the tool's definition The tool name 'puppeteer_get_element_info' and description 'Get detailed information about an element' indicate a query/retrieval operation. It retrieves information about DOM elements without modifying state or executing commands.

Documented attack patterns abuse exactly the kind of access puppeteer_get_element_info gives an agent:

POLICY

How to control puppeteer_get_element_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude TypeScript MCP Servers, and nothing reaches the server without passing your rules. This is the rule we recommend for puppeteer_get_element_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "puppeteer_get_element_info": {}
  }
}

puppeteer_get_element_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Claude TypeScript MCP Servers — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude TypeScript MCP Servers tools

Destructive delete_file Delete a file. This operation cannot be undone. Only works within allowed directories. Destructive delete_release Delete a release Execute puppeteer_clear_input Clear an input field Execute batch_operations Execute multiple file operations efficiently. Supports transactional mode (rollback on err Execute puppeteer_emulate_device Emulate a specific device Execute puppeteer_evaluate Execute JavaScript in the browser console Execute puppeteer_evaluate_in_frame Execute JavaScript in a specific frame Execute puppeteer_navigate Navigate to a URL

All 84 Claude TypeScript MCP Servers tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about puppeteer_get_element_info

What does the puppeteer_get_element_info tool do? +

Get detailed information about an element. It is categorised as a Read tool in the Claude TypeScript MCP Servers MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on puppeteer_get_element_info? +

Register the Claude TypeScript MCP Servers MCP server in PolicyLayer and add a rule for puppeteer_get_element_info: 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 Claude TypeScript MCP Servers. Nothing to install.

What risk level is puppeteer_get_element_info? +

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

Can I rate-limit puppeteer_get_element_info? +

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

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

puppeteer_get_element_info is provided by the Claude TypeScript MCP Servers MCP server (ukkz/claude-ts-mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude TypeScript MCP Servers tool call.

Start from Claude TypeScript MCP Servers, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →