solved.ac 태그 카탈로그를 강제로 다시 로드합니다.
AI agents invoke solvedac_refresh_tag_catalog to trigger actions in BOJ 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.
This tool forcibly triggers a reload/refresh operation of the tag catalog, which is an active execution of an external process rather than a passive read. It has side effects on the server's internal state (refreshing cached data). It does not delete or overwrite data irreversibly, nor does it write user data, so Execute is the most appropriate category.
From the tool's definition '강제로 다시 로드합니다' (forcibly reloads) — triggers an external operation to force-refresh/reload the tag catalog
Attacks that exploit this kind of access
solved.ac 태그 카탈로그를 강제로 다시 로드합니다. It is categorised as a Execute tool in the BOJ MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the BOJ MCP Server MCP server in PolicyLayer and add a rule for solvedac_refresh_tag_catalog: 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 BOJ MCP Server. Nothing to install.
solvedac_refresh_tag_catalog 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 solvedac_refresh_tag_catalog 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 solvedac_refresh_tag_catalog. 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.
solvedac_refresh_tag_catalog is provided by the BOJ MCP Server MCP server (junwoo-seo-1998/boj-mcp-server). 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 →