get_distribution_info
AI agents call get_distribution_info to retrieve information from EMBA-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context indicate this retrieves distribution/OS information from firmware analysis results. Like its sibling tools (get_kernel_info, get_bootloader_info, get_filesystem_overview), it appears to be a read-only query operation that returns analyzed data without modifying or executing anything.
From the tool's definition Tool name 'get_distribution_info' and context as a query tool on an EMBA firmware analysis server that exposes 'structured security findings' alongside sibling tools like get_kernel_info, get_bootloader_info, and get_filesystem_overview.
Documented attack patterns abuse exactly the kind of access get_distribution_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EMBA-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_distribution_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_distribution_info": {}
}
}get_distribution_info 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.
get_distribution_info. It is categorised as a Read tool in the EMBA-MCP MCP Server, which means it retrieves data without modifying state.
Register the EMBA- MCP server in PolicyLayer and add a rule for get_distribution_info: 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 EMBA-MCP. Nothing to install.
get_distribution_info 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_distribution_info 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_distribution_info. 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_distribution_info is provided by the EMBA- MCP server (0xbuz3r/emba-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from EMBA-MCP, 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.
20 EMBA-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.