get_egress_policy
Read a project's egress allow-list policy (enabled, allowlist, recently-blocked hosts).
This record as markdown: /tools/denkopsai-mcp/get-egress-policy.md
What get_egress_policy does on Denkopsai
AI agents call get_egress_policy to retrieve information from Denkopsai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project_id | string | Yes |
Parameters from the server's own tool schema.
Why get_egress_policy is rated Low
This tool only reads and queries existing egress policy configuration data. It returns informational state about firewall rules and restrictions without creating, modifying, or deleting any resources. The blast radius of misuse is limited to information disclosure about network policies.
From the tool's definition Tool name contains 'get_' prefix and description explicitly states 'Read a project's egress allow-list policy'. The function retrieves policy configuration (enabled status, allowlist entries, blocked hosts) with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_egress_policy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_egress_policy, this is the rule to start with:
get_egress_policy 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 Denkopsai, apply this rule, and every get_egress_policy call is checked against it from then on.
Questions about get_egress_policy
Read a project's egress allow-list policy (enabled, allowlist, recently-blocked hosts). It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.
get_egress_policy accepts 1 parameter: project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for get_egress_policy: 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 Denkopsai. Nothing to install.
get_egress_policy 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_egress_policy 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_egress_policy. 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_egress_policy is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
This server
Across the catalogue