Create a security group ingress rule
AI agents use create_security_group_rule to create or update resources in CloudStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.
Creating security group rules is a write operation that modifies cloud infrastructure configuration. While security rules can be deleted (reversible), they directly impact network access control and can expose resources to unintended traffic or attacks if misconfigured by an AI agent.
From the tool's definition Tool name 'create_security_group_rule' and description 'Create a security group ingress rule' explicitly indicate creation/modification of firewall/network access control rules. This is a reversible write operation that modifies network security configuration.
Documented attack patterns abuse exactly the kind of access create_security_group_rule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CloudStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_security_group_rule:
{
"version": "1",
"default": "deny",
"tools": {
"create_security_group_rule": {
"limits": [
{
"counter": "create_security_group_rule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_security_group_rule stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a security group ingress rule. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for create_security_group_rule: 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 CloudStack MCP Server. Nothing to install.
create_security_group_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_security_group_rule 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 create_security_group_rule. 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.
create_security_group_rule is provided by the CloudStack MCP Server MCP server (phantosmax/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CloudStack 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.
45 CloudStack MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.