get_tracked_components

SERVERWhy Did You Render SOURCE0x1f320/why-did-you-render-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/0x1f320-why-did-you-render-mcp/get-tracked-components.md

WHAT IT DOES

What get_tracked_components does on Why Did You Render

AI agents call get_tracked_components to retrieve information from Why Did You Render without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_tracked_components is rated Low

This tool queries and returns existing configuration and observational data from a React performance monitoring system. It has no side effects, does not create, modify, or delete data, and does not execute code or perform destructive operations. The blast radius of misuse is minimal—an agent could only access render tracking information about the connected project, which is non-sensitive performance metadata.

From the tool's definition The tool description explicitly states it 'Returns' configuration data and 'shows components observed in render data.' The verb 'Returns' and the read-only nature of retrieving tracking configuration and observed component information without any data…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_tracked_components safely

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

get_tracked_components Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Why Did You Render, apply this rule, and every get_tracked_components call is checked against it from then on.

FAQ

Questions about get_tracked_components

What does the get_tracked_components tool do? +

Returns the why-did-you-render configuration for the connected project, including include/exclude filters and tracking options. Also shows components observed in render data. If multiple projects are active and no project is specified, the tool will ask you to disambiguate. It is categorised as a Read tool in the Why Did You Render MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tracked_components? +

Register the Why Did You Render MCP server in PolicyLayer and add a rule for get_tracked_components: 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 Why Did You Render. Nothing to install.

What risk level is get_tracked_components? +

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

Can I rate-limit get_tracked_components? +

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

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

get_tracked_components is provided by the Why Did You Render MCP server (0x1f320/why-did-you-render-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Why Did You Render, and thousands of servers like it.

This server

All 14 Why Did You Render tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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