작업 실행 이력 조회
AI agents call scheduler_history 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 is a read-only operation that queries or lists historical execution records. No data is modified, deleted, or created. No code is executed and no financial operations occur. The blast radius if misused is minimal — worst case an agent learns about past task execution patterns, which poses no direct harm to systems or data.
From the tool's definition Tool name is 'scheduler_history' and description translates to 'query work execution history' — a retrieval operation. The tool accesses historical logs or records of previously executed tasks without modifying, deleting, or executing anything new.
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_history: 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_history 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_history 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_history. 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_history 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 →