AI agents call decompile_dotnet_assembly to retrieve information from Binary MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and server context (ILSpyCmd is a .NET decompiler), this tool likely reads and decompiles a .NET assembly into readable source code. This is a read/analysis operation with no side effects. Confidence is lowered due to empty description. Severity is medium because decompiling binaries could expose sensitive intellectual property or internal logic.
From the tool's definition Tool name 'decompile_dotnet_assembly' and server context mentioning ILSpyCmd for .NET analysis; description is empty.
Documented attack patterns abuse exactly the kind of access decompile_dotnet_assembly gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Binary MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for decompile_dotnet_assembly:
{
"version": "1",
"default": "deny",
"tools": {
"decompile_dotnet_assembly": {}
}
}decompile_dotnet_assembly 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.
decompile_dotnet_assembly. It is categorised as a Read tool in the Binary MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Binary MCP Server MCP server in PolicyLayer and add a rule for decompile_dotnet_assembly: 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 Binary MCP Server. Nothing to install.
decompile_dotnet_assembly 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 decompile_dotnet_assembly 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 decompile_dotnet_assembly. 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.
decompile_dotnet_assembly is provided by the Binary MCP Server MCP server (sarks0/binary-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Binary 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.
59 Binary MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.