Submit a file for basic analysis using the OpenTIP API.
AI agents invoke analyze_file to trigger actions in Kaspersky OpenTIP MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Submitting a file to an external API for analysis is an active operation that triggers processing on a remote system. It is not a pure read (it sends data outbound), not a write to a local store, and not destructive or financial. 'Execute' best captures that it dispatches an external operation (file analysis pipeline) whose behavior depends on the submitted file.
From the tool's definition "Submit a file for basic analysis" — the tool actively submits/triggers an external analysis operation via the OpenTIP API, whose effects depend on the file argument provided.
Documented attack patterns abuse exactly the kind of access analyze_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kaspersky OpenTIP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_file:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_file": {
"limits": [
{
"counter": "analyze_file_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}analyze_file stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Submit a file for basic analysis using the OpenTIP API. It is categorised as a Execute tool in the Kaspersky OpenTIP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kaspersky OpenTIP MCP Server MCP server in PolicyLayer and add a rule for analyze_file: 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 Kaspersky OpenTIP MCP Server. Nothing to install.
analyze_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the analyze_file 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 analyze_file. 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.
analyze_file is provided by the Kaspersky OpenTIP MCP Server MCP server (kasperskylab/threat-intelligence). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kaspersky OpenTIP MCP Server, 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.
6 Kaspersky OpenTIP MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.