AI agents use create_monitor to create or update resources in Uptrack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Uptrack environment.
This tool creates (writes) a new monitor configuration in the Uptrack uptime monitoring system. It is reversible via the sibling tool 'delete_monitor', making it Write rather than Destructive.
From the tool's definition Tool name is 'create_monitor' and description states 'Create a new uptime monitor', indicating creation of a new monitoring resource.
Attacks that exploit this kind of access
Create a new uptime monitor. It is categorised as a Write tool in the Uptrack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Uptrack MCP server in PolicyLayer and add a rule for create_monitor: 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 Uptrack. Nothing to install.
create_monitor 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_monitor 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_monitor. 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_monitor is provided by the Uptrack MCP server (uptrack-app/uptrack-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 →