Low Risk

get_attributes

Получить атрибуты элемента

How to control get_attributes ↓

What get_attributes does on Yandex Browser MCP Server

AI agents call get_attributes to retrieve information from Yandex Browser MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_attributes needs a policy

This tool queries and retrieves data (DOM element attributes) without side effects. It does not modify, execute, delete, or create anything. It is a passive information retrieval operation, consistent with the Read category definition.

From the tool's definition Tool name is 'get_attributes' and description translates to 'Get element attributes'. The function retrieves element properties from the DOM without modifying state.

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

How to control get_attributes

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

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

get_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 Yandex Browser MCP Server — 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 get_attributes

What does the get_attributes tool do? +

Получить атрибуты элемента. It is categorised as a Read tool in the Yandex Browser MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_attributes? +

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

What risk level is get_attributes? +

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

Can I rate-limit get_attributes? +

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

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

get_attributes is provided by the Yandex Browser MCP Server MCP server (t1trit/yandex-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Yandex Browser MCP Server tool call.

Start from Yandex Browser MCP Server, 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.

18 Yandex Browser MCP Server 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.