Low Risk

extract.attributes

Extract attributes from elements matching CSS selectors

How to control extract.attributes ↓

What extract.attributes does on LCBro

AI agents call extract.attributes to retrieve information from LCBro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why extract.attributes needs a policy

This tool reads/queries DOM attributes from elements on a page using CSS selectors. It only retrieves data without modifying state, executing code, or causing any side effects. Severity is low as it can only read page content.

From the tool's definition Extract attributes from elements matching CSS selectors

Documented attack patterns abuse exactly the kind of access extract.attributes gives an agent:

How to control extract.attributes

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "extract.attributes": {}
  }
}

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

  1. Create a free account and register LCBro — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about extract.attributes

What does the extract.attributes tool do? +

Extract attributes from elements matching CSS selectors. It is categorised as a Read tool in the LCBro MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on extract.attributes? +

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

What risk level is extract.attributes? +

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

Can I rate-limit extract.attributes? +

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

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

extract.attributes is provided by the LCBro MCP server (lcbro/lcbro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LCBro tool call.

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

Free to start. No card required.

11 LCBro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.