file_info
AI agents call file_info to retrieve information from Browser Automation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a read-only query operation that retrieves information about files. Even in the absence of a description, the naming convention and context of sibling tools support classification as Read. The empty description reduces confidence slightly, but the semantic meaning of 'file_info' strongly suggests metadata retrieval with no side effects.
From the tool's definition Tool name 'file_info' suggests retrieval of file metadata or information. The description is empty, but given the server context (browser automation and content scraping) and sibling tools like 'read_file_content', 'preview_file', and 'list_directory', this…
Attacks that exploit this kind of access
file_info. It is categorised as a Read tool in the Browser Automation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browser Automation MCP Server MCP server in PolicyLayer and add a rule for file_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 Browser Automation MCP Server. Nothing to install.
file_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 file_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 file_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.
file_info is provided by the Browser Automation MCP Server MCP server (raghu6798/browser_scrape_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 →