get_page_info

THE RISK

Low Risk

Why get_page_info needs a policy

This tool retrieves static information about a webpage (URL, title, meta-tags) without modifying data, executing code, or triggering side effects. It is a pure read operation with minimal security risk, even if misused by an AI agent, as it only exposes publicly available page metadata.

From the tool's definition Tool name 'get_page_info' and description 'Получить информацию о странице (URL, заголовок, мета-теги)' [Get information about the page (URL, title, meta-tags)] indicate retrieval of page metadata only.

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

POLICY

How to control get_page_info

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_page_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_page_info": {}
  }
}

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

Create a free account and register Yandex Browser MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Yandex Browser MCP Server tools

Execute execute_test Выполнить тест в указанной вкладке: выбрать ответы и отправить Execute navigate Перейти по URL в указанной вкладке Execute wait_for_element Ждать появления элемента Execute evaluate Выполнить JavaScript код в указанной вкладке Execute hover Навести курсор на элемент Execute click Кликнуть по элементу в указанной вкладке Execute connect_to_browser Подключиться к уже открытому Яндекс Браузеру Execute key_press Нажать клавишу или комбинацию клавиш

All 18 Yandex Browser MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_page_info

What does the get_page_info tool do? +

Получить информацию о странице (URL, заголовок, мета-теги). 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_page_info? +

Register the Yandex Browser MCP Server MCP server in PolicyLayer and add a rule for get_page_info: 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_page_info? +

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

Can I rate-limit get_page_info? +

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

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

get_page_info 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.

CHECK YOUR STACK →