Creates a new self-signed certificate
AI agents use mikrotik_create_certificate to create or update resources in MikroTik Cursor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MikroTik Cursor MCP environment.
This tool creates and stores a new certificate on the MikroTik router. While certificate creation is reversible (certificates can be deleted), it modifies router state and could be misused to generate certificates for spoofing, man-in-the-middle attacks, or unauthorized TLS configurations if an AI agent is compromised.
From the tool's definition Tool name explicitly states 'create_certificate' and description confirms 'Creates a new self-signed certificate' — this is a creation operation that adds new data to the router's certificate store.
Attacks that exploit this kind of access
Creates a new self-signed certificate. It is categorised as a Write tool in the MikroTik Cursor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_create_certificate: 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 MikroTik Cursor MCP. Nothing to install.
mikrotik_create_certificate 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 mikrotik_create_certificate 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 mikrotik_create_certificate. 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.
mikrotik_create_certificate is provided by the MikroTik Cursor MCP server (kevinpez/mikrotik-cursor-mcp). 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 →