Get source location for a specific attribute path
AI agents call view_attribute_source to retrieve information from React Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves source location information for debugging purposes, which is informational and non-destructive. It has no side effects beyond querying state. It does not modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only learn where code is located, not alter it or trigger unwanted operations.
From the tool's definition Tool name 'view_attribute_source' and description 'Get source location for a specific attribute path' indicate retrieval of metadata (source code location) with no modification, deletion, or execution. This is a read-only inspection operation.
Attacks that exploit this kind of access
Get source location for a specific attribute path. It is categorised as a Read tool in the React Devtools MCP Server, which means it retrieves data without modifying state.
Register the React Devtools MCP server in PolicyLayer and add a rule for view_attribute_source: 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 React Devtools. Nothing to install.
view_attribute_source is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the view_attribute_source 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.
Set action: deny in the PolicyLayer policy for view_attribute_source. 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.
view_attribute_source is provided by the React Devtools MCP server (skylarbarrera/react-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →