set_alert_scripting

[HTTP mode only] Save alert scripting configuration or rules for a specific counter. Use

Server Scouter scouter-mcp-server
Category Write
Risk class Medium
Parameters 00 required

What set_alert_scripting does on Scouter

AI agents use set_alert_scripting to create or update resources in Scouter — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scouter environment.

Why set_alert_scripting needs a policy

This tool modifies alert scripting rules and configuration, which is a reversible write operation. Severity is high because misconfigured alerts could suppress critical warnings or trigger false alarms affecting incident response, though the operation itself is not destructive or financial. Confidence is slightly reduced (0.85) due to the incomplete description, but the intent is clear from the name and 'Save' verb.

From the tool's definition Tool name 'set_alert_scripting' and description 'Save alert scripting configuration or rules' indicate creation/modification of alert rules. The 'set_' prefix and 'Save' verb confirm a write operation that persists configuration changes.

Questions about set_alert_scripting

What does the set_alert_scripting tool do? +

[HTTP mode only] Save alert scripting configuration or rules for a specific counter. Use. It is categorised as a Write tool in the Scouter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_alert_scripting? +

Register the Scouter MCP server in PolicyLayer and add a rule for set_alert_scripting: 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 Scouter. Nothing to install.

What risk level is set_alert_scripting? +

set_alert_scripting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_alert_scripting? +

Yes. Add a rate_limit block to the set_alert_scripting 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.

How do I block set_alert_scripting completely? +

Set action: deny in the PolicyLayer policy for set_alert_scripting. 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.

What MCP server provides set_alert_scripting? +

set_alert_scripting is provided by the Scouter MCP server (scouter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.