collect_devtools_data

Collect current DevTools data from monitored page

SERVERPercepta MCP Server SOURCE0x-hewm/percepta-mcp

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/0x-hewm-percepta-mcp/collect-devtools-data.md

WHAT IT DOES

What collect_devtools_data does on Percepta MCP Server

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

RISK

Why collect_devtools_data is rated Low

This tool retrieves diagnostic and monitoring information from browser DevTools on an already-loaded page. It performs no side effects, does not modify state, does not execute arbitrary code, and does not delete data. The action is purely observational—gathering existing telemetry or metrics from the page's development tools.

From the tool's definition Tool name 'collect_devtools_data' and description 'Collect current DevTools data from monitored page' indicate passive data retrieval. Uses words 'Collect' and 'current' suggesting query/fetch operations without modification or execution of code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs collect_devtools_data safely

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

collect_devtools_data Allowed

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

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

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

FAQ

Questions about collect_devtools_data

What does the collect_devtools_data tool do? +

Collect current DevTools data from monitored page. It is categorised as a Read tool in the Percepta MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on collect_devtools_data? +

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

What risk level is collect_devtools_data? +

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

Can I rate-limit collect_devtools_data? +

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

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

collect_devtools_data is provided by the Percepta MCP Server MCP server (0x-hewm/percepta-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Percepta MCP Server, and thousands of servers like it.

This server

All 22 Percepta MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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