scheduler_run_job | PolicyLayer

WHAT IT DOES

What scheduler_run_job does on PM-MCP (Portfolio Management MCP Server)

AI agents invoke scheduler_run_job to trigger actions in PM-MCP (Portfolio Management 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 scheduler_run_job needs a policy

This tool executes external operations (scheduled jobs) whose effects depend on the job arguments/configuration. While not immediately destructive or financial by itself, it is a trigger for automated operations that could perform any action (data retrieval, trades, report generation, etc.). This fits the Execute category as it runs code/operations whose impact is contingent on arguments.

From the tool's definition Tool name 'scheduler_run_job' combined with description '특정 작업 즉시 실행' (run a specific job immediately) indicates the tool triggers execution of scheduled jobs on demand.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

scheduler_run_job Rate-limited

scheduler_run_job 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": {
    "scheduler_run_job": {
      "limits": [
        {
          "counter": "scheduler_run_job_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 PM-MCP (Portfolio Management MCP Server), so you can run agents against it safely.

FAQ

Questions about scheduler_run_job

What does the scheduler_run_job tool do? +

특정 작업 즉시 실행. It is categorised as a Execute tool in the PM-MCP (Portfolio Management 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 scheduler_run_job? +

Register the PM-MCP (Portfolio Management MCP Server) MCP server in PolicyLayer and add a rule for scheduler_run_job: 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 PM-MCP (Portfolio Management MCP Server). Nothing to install.

What risk level is scheduler_run_job? +

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

Can I rate-limit scheduler_run_job? +

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

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

scheduler_run_job is provided by the PM-MCP (Portfolio Management MCP Server) MCP server (surplus96/pm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.