schedule_start_application · AWS IoT SiteWise MCP Server MCP

WHAT IT DOES

What schedule_start_application does on AWS IoT SiteWise MCP Server

AI agents invoke schedule_start_application to trigger actions in AWS IoT SiteWise MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why schedule_start_application needs a policy

The name suggests scheduling and starting an application, which falls under Execute (triggering external operations). Without a description, confidence is reduced, but the action of starting/scheduling an application is most analogous to Execute. Severity is high because starting industrial IoT applications (SiteWise context) could have significant operational impact.

From the tool's definition Tool name 'schedule_start_application' implies triggering or starting an application execution; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_start_application Rate-limited

schedule_start_application stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "schedule_start_application": {
      "limits": [
        {
          "counter": "schedule_start_application_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AWS IoT SiteWise MCP Server, so you can run agents against it safely.

FAQ

Questions about schedule_start_application

What does the schedule_start_application tool do? +

schedule_start_application. It is categorised as a Execute tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on schedule_start_application? +

Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for schedule_start_application: 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 AWS IoT SiteWise MCP Server. Nothing to install.

What risk level is schedule_start_application? +

schedule_start_application is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit schedule_start_application? +

Yes. Add a rate_limit block to the schedule_start_application 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 schedule_start_application completely? +

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

schedule_start_application is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.