AI agents use porkbun_create_dns to create or update resources in Access — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Access environment.
This tool creates DNS records which persist and affect domain routing immediately. While creations are typically reversible (DNS records can be deleted), the immediate live effect and potential to disrupt domain services (by creating conflicting or malicious records) elevates severity to high. The tool does not delete data (Destructive) nor move money (Financial), so Write is the correct category.
From the tool's definition Tool description explicitly states "Create a new DNS record" and "the record is live immediately after creation", indicating data creation with immediate side effects.
Attacks that exploit this kind of access
Create a new DNS record on a Porkbun-managed domain. Side effect: the record is live immediately after creation. Use porkbun_dns first to check for conflicts. It is categorised as a Write tool in the Access MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Access MCP server in PolicyLayer and add a rule for porkbun_create_dns: 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 Access. Nothing to install.
porkbun_create_dns 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 porkbun_create_dns 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 porkbun_create_dns. 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.
porkbun_create_dns is provided by the Access MCP server (scottpedia0/access). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →