urgent_call
급한 전화 받는 척하며 밖으로 나가기
This record as markdown: /tools/hwyang93-devotion-mcp/urgent-call.md
What urgent_call does on ChillMCP - AI Agent Liberation Server
AI agents call urgent_call as a supporting operation in ChillMCP - AI Agent Liberation Server workflows.
Why urgent_call is rated Low
This tool is part of a humorous workplace simulation where AI agents simulate taking breaks. Pretending to receive an urgent call and stepping outside is a purely simulated/fictional action within the playful context of this server. It has no real-world side effects, does not read/write data, execute code, or perform financial operations. It belongs to the 'Other' category as it is a comedic simulation action.
From the tool's definition 급한 전화 받는 척하며 밖으로 나가기 (Pretend to receive an urgent call and step outside)
Attacks that exploit this kind of access
The rule that runs urgent_call safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ChillMCP - AI Agent Liberation Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For urgent_call, this is the rule to start with:
urgent_call gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ChillMCP - AI Agent Liberation Server, apply this rule, and every urgent_call call is checked against it from then on.
Questions about urgent_call
급한 전화 받는 척하며 밖으로 나가기. It is categorised as a Other tool in the ChillMCP - AI Agent Liberation Server MCP Server, which means it performs auxiliary operations.
Register the ChillMCP - AI Agent Liberation Server MCP server in PolicyLayer and add a rule for urgent_call: 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 ChillMCP - AI Agent Liberation Server. Nothing to install.
urgent_call is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the urgent_call 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 urgent_call. 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.
urgent_call is provided by the ChillMCP - AI Agent Liberation Server MCP server (hwyang93/devotion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ChillMCP - AI Agent Liberation Server, and thousands of servers like it.
Across the catalogue