Create a campsite availability alert that monitors for openings and notifies the user. Requires an Outdoorithm API key (generate at outdoorithm.com/dashboard/api-keys). The alert runs continuously, checking every 2-15 minutes depending on subscription tier. Args: api_key: User's Outdoorithm API k...
Risk signalsHandles credentials or secrets (api_key) · High parameter count (12 properties)
Part of the Outdoorithm server.
Free to start. No card required.
AI agents use create_alert to create or modify resources in Outdoorithm. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_alert repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Outdoorithm.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"create_alert": {
"limits": [
{
"counter": "create_alert_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Outdoorithm policy for all 18 tools.
These attack patterns abuse exactly the kind of access create_alert gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Create a campsite availability alert that monitors for openings and notifies the user. Requires an Outdoorithm API key (generate at outdoorithm.com/dashboard/api-keys). The alert runs continuously, checking every 2-15 minutes depending on subscription tier. Args: api_key: User's Outdoorithm API key from their dashboard settings. campground_ids: List of campground CUIDs to monitor. All must use the same reservation provider. Get CUIDs from search_campgrounds or get_campground_details. Example: ["RecreationDotGov:232447:2991"] start_date: Earliest check-in date to monitor (YYYY-MM-DD). Required for all date types. end_date: Latest check-out date (YYYY-MM-DD). Required when date_type is "range". date_type: How dates are interpreted. "range" monitors a specific date window (default), "perpetual" monitors rolling 6 months from start_date, "specific_months" monitors only certain months each year. specific_months: Month numbers 1-12 to monitor. Required when date_type is "specific_months". min_nights: Minimum consecutive nights needed (1-14, default 1). max_nights: Maximum consecutive nights (1-14, must be >= min_nights). Omit for no max. days_of_week: Preferred check-in days as integers (0=Monday through 6=Sunday). Omit for any day. notify_email: Send email when availability found (default true). notify_sms: Send SMS when availability found (default false, requires phone on account). name: Display name for this alert. Auto-generated from campground and dates if omitted.. It is categorised as a Write tool in the Outdoorithm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outdoorithm MCP server in PolicyLayer and add a rule for create_alert: 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 Outdoorithm. Nothing to install.
create_alert 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_alert 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_alert. 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_alert is provided by the Outdoorithm MCP server (https://mcp.outdoorithm.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Outdoorithm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.