文件信誉报告：获取文件详细的静态和动态分析报告，包括威胁等级、行为签名、网络行为等
AI agents call file_analysis to retrieve information from ThreatMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries existing analysis reports for files from ThreatBook's threat intelligence platform. It reads and returns data (threat level, behavioral signatures, network behavior) without modifying, executing, or deleting anything. Severity is medium because it accesses sensitive threat intelligence data that could reveal security posture or be misused for reconnaissance.
From the tool's definition 获取文件详细的静态和动态分析报告，包括威胁等级、行为签名、网络行为等 (retrieve detailed static and dynamic analysis reports including threat level, behavioral signatures, network behavior)
Documented attack patterns abuse exactly the kind of access file_analysis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ThreatMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for file_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"file_analysis": {}
}
}file_analysis is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
文件信誉报告：获取文件详细的静态和动态分析报告，包括威胁等级、行为签名、网络行为等. It is categorised as a Read tool in the ThreatMCP MCP Server, which means it retrieves data without modifying state.
Register the Threat MCP server in PolicyLayer and add a rule for file_analysis: 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 ThreatMCP. Nothing to install.
file_analysis 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_analysis 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_analysis. 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_analysis is provided by the Threat MCP server (naxg/threatmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ThreatMCP, 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.
15 ThreatMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.