get_malware_report
Get detailed malware report for a hosting package
This record as markdown: /tools/cbrown35-20i-mcp/get-malware-report.md
What get_malware_report does on 20i MCP Server
AI agents call get_malware_report to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_malware_report is rated Low
This tool retrieves and queries malware report information associated with a hosting package. It is a read-only operation that returns data without side effects, reversible changes, or irreversible modifications. The blast radius of misuse is minimal—an attacker gains visibility into security status but cannot alter configurations, delete data, execute code, or move money.
From the tool's definition Tool name 'get_malware_report' and description 'Get detailed malware report for a hosting package' indicate retrieval of existing report data with no modification, deletion, or execution of operations.
Attacks that exploit this kind of access
The rule that runs get_malware_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_malware_report, this is the rule to start with:
get_malware_report 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 20i MCP Server, apply this rule, and every get_malware_report call is checked against it from then on.
Questions about get_malware_report
Get detailed malware report for a hosting package. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_malware_report: 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 20i MCP Server. Nothing to install.
get_malware_report 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_malware_report 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_malware_report. 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_malware_report is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue