set_alert_priority
Set operator priority for one or more alerts.
This record as markdown: /tools/secure-ssid-centralmcp/set-alert-priority.md
What set_alert_priority does on API-Central
AI agents use set_alert_priority to create or update resources in API-Central, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.
Why set_alert_priority is rated Medium
This tool modifies alert metadata (priority level) which is a reversible change to system state. It does not delete data (not Destructive), execute arbitrary operations (not Execute), move money (not Financial), or merely retrieve information (not Read). The medium severity reflects that misconfigured alert priorities could degrade incident response effectiveness, but the impact is containable and reversible.
From the tool's definition Tool name is 'set_alert_priority' and description states it 'Set operator priority for one or more alerts.' The verb 'set' and action of modifying alert priority attributes indicate data modification.
Attacks that exploit this kind of access
The rule that runs set_alert_priority safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_alert_priority, this is the rule to start with:
set_alert_priority 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.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every set_alert_priority call is checked against it from then on.
Questions about set_alert_priority
Set operator priority for one or more alerts. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the API-Central MCP server in PolicyLayer and add a rule for set_alert_priority: 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 API-Central. Nothing to install.
set_alert_priority 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 set_alert_priority 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 set_alert_priority. 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.
set_alert_priority is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue