This record as markdown: /tools/dev-bugezy-bugezy/get-page-info.md
What get_page_info does on BugEzy
AI agents call get_page_info to retrieve information from BugEzy without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
report_id | string | Yes |
Parameters from the server's own tool schema.
Why get_page_info is rated Low
Even though get_page_info only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_page_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and BugEzy, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_page_info, this is the rule to start with:
get_page_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect BugEzy, apply this rule, and every get_page_info call is checked against it from then on.
Questions about get_page_info
取得頁面資訊（URL/標題/瀏覽器/解析度）。Page info. It is categorised as a Read tool in the BugEzy MCP Server, which means it retrieves data without modifying state.
get_page_info accepts 1 parameter: report_id. Required: report_id. The full parameter table on this page comes from the server's own tool schema.
Register the BugEzy 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 BugEzy. Nothing to install.
get_page_info 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 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.
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.
get_page_info is provided by the BugEzy MCP server (https://bugezy.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on BugEzy, and thousands of servers like it.
This server
Across the catalogue