AI agents call file_analyze to retrieve information from Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | — | Input format (default: auto-detect) |
content | string | Yes | File content (raw text or base64) |
options | object | — | |
encoding | string | — | Content encoding (default: utf-8) |
Parameters from the server's own tool schema.
file_analyze retrieves information and performs read-only analysis operations on data. It detects types, computes descriptive statistics, and returns results without creating, modifying, or deleting data. This is a classic Read operation. Low severity because misuse simply produces incorrect analysis output with minimal blast radius.
From the tool's definition Tool analyzes and computes statistics on tabular data: 'detect column types, compute stats (min/max/mean/median for numbers, top values for text), find nulls.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
Analyze tabular data: detect column types, compute stats (min/max/mean/median for numbers, top values for text), find nulls. Returns summary and preview. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
file_analyze accepts 4 parameters: format, content, options, encoding. Required: content. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for file_analyze: 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 Tools. Nothing to install.
file_analyze 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_analyze 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_analyze. 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_analyze is provided by the Tools MCP server (https://www.jiebang.site/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 →