서킷 브레이커 리셋 (name 미지정 시 전체 리셋)
AI agents invoke circuit_reset 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.
A circuit breaker reset triggers a state change in an operational safety/control mechanism. This is an Execute-level action: it modifies the runtime state of external systems (circuit breakers) and can have broad blast radius if all breakers are reset simultaneously (re-enabling previously blocked operations).
From the tool's definition '서킷 브레이커 리셋 (name 미지정 시 전체 리셋)' — resets circuit breaker(s), optionally resetting all if no name is specified
Attacks that exploit this kind of access
서킷 브레이커 리셋 (name 미지정 시 전체 리셋). 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.
Register the PM-MCP (Portfolio Management MCP Server) MCP server in PolicyLayer and add a rule for circuit_reset: 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.
circuit_reset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the circuit_reset 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 circuit_reset. 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.
circuit_reset 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 →