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

network_create

Crea una red Docker. Parametros: name (requerido), driver (default

SERVERMCP Framework Personal SOURCEinggerman/mcps
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/inggerman-mcps/network-create.md

What network_create does on MCP Framework Personal

AI agents invoke network_create to trigger actions in MCP Framework Personal. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why network_create is rated High

Creating a Docker network is an external infrastructure operation with side effects beyond simple data writes. It provisions networking resources in the Docker daemon, which is an Execute-level action. It is reversible (networks can be deleted), so it doesn't reach Destructive, but it does trigger real external system changes beyond a simple data write.

From the tool's definition 'Crea una red Docker' (Creates a Docker network) — triggers an external Docker infrastructure operation

Questions about network_create

What does the network_create tool do? +

Crea una red Docker. Parametros: name (requerido), driver (default. It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on network_create? +

Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for network_create: 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 MCP Framework Personal. Nothing to install.

What risk level is network_create? +

network_create is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit network_create? +

Yes. Add a rate_limit block to the network_create 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 network_create completely? +

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

network_create is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on MCP Framework Personal, 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 MCP Framework Personal'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.