New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_egress_policy

Set a project's egress allow-list. enabled=true is zero-trust default-deny; only listed hosts (exact or *.domain) may egress. Allow-list edits apply live; enabling/disabling applies on the next deploy.

SERVERDenkopsai SOURCE@denkopsai/mcp
Medium RISK CLASS
Category Write
Parameters 33 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/denkopsai-mcp/set-egress-policy.md

What set_egress_policy does on Denkopsai

AI agents use set_egress_policy to create or update resources in Denkopsai, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Denkopsai environment.

ParameterTypeRequiredDescription
enabled boolean Yes
allowlist array Yes
project_id string Yes

Parameters from the server's own tool schema.

Why set_egress_policy is rated Medium

This tool modifies security infrastructure (egress policies) but does not irreversibly delete data, nor does it execute arbitrary code or move money. It is a Write operation that creates/modifies configuration settings.

From the tool's definition Tool description states 'Set a project's egress allow-list' and 'Allow-list edits apply live', indicating modification of security policy configuration. The tool creates or modifies network policy settings that are applied immediately or on next deploy.

Questions about set_egress_policy

What does the set_egress_policy tool do? +

Set a project's egress allow-list. enabled=true is zero-trust default-deny; only listed hosts (exact or *.domain) may egress. Allow-list edits apply live; enabling/disabling applies on the next deploy. It is categorised as a Write tool in the Denkopsai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does set_egress_policy accept? +

set_egress_policy accepts 3 parameters: enabled, allowlist, project_id. Required: enabled, allowlist, project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on set_egress_policy? +

Register the Denkopsai MCP server in PolicyLayer and add a rule for set_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.

What risk level is set_egress_policy? +

set_egress_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_egress_policy? +

Yes. Add a rate_limit block to the set_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.

How do I block set_egress_policy completely? +

Set action: deny in the PolicyLayer policy for set_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.

What MCP server provides set_egress_policy? +

set_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Denkopsai's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.