스케줄러 상태 조회: 실행 중인 작업, 다음 실행 시간, 최근 이력
AI agents call scheduler_status to retrieve information from PM-MCP (Portfolio Management MCP Server) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays scheduler status information without creating, modifying, executing, or deleting any data. It is purely informational, querying the state of existing scheduled operations. Low severity due to minimal blast radius if misused—an AI agent could only read scheduling metadata, which poses no security or financial risk.
From the tool's definition Tool description indicates '상태 조회' (status inquiry) of scheduler operations, tasks, and execution history. Key phrases: '실행 중인 작업' (running tasks), '다음 실행 시간' (next execution time), '최근 이력' (recent history).
Attacks that exploit this kind of access
스케줄러 상태 조회: 실행 중인 작업, 다음 실행 시간, 최근 이력. It is categorised as a Read tool in the PM-MCP (Portfolio Management MCP Server) MCP Server, which means it retrieves data without modifying state.
Register the PM-MCP (Portfolio Management MCP Server) MCP server in PolicyLayer and add a rule for scheduler_status: 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.
scheduler_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the scheduler_status 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 scheduler_status. 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.
scheduler_status 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.
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 →