KUPID 공지사항의 상세 내용을 조회합니다.
AI agents call kupid_get_notice_detail to retrieve information from Ku Portal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves notice details from the KUPID portal, which is a read-only query operation. It fetches existing data without creating, modifying, deleting, or executing external operations. The blast radius is minimal—misuse would only result in unauthorized information disclosure of academic notices, not data modification or financial impact. Categorized as Read with low severity.
From the tool's definition Tool name 'kupid_get_notice_detail' and description '공지사항의 상세 내용을 조회합니다' (retrieve detailed content of notices) indicate data retrieval only. The verb '조회' (query/retrieve) is a read-only operation with no side effects.
Documented attack patterns abuse exactly the kind of access kupid_get_notice_detail gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ku Portal, and nothing reaches the server without passing your rules. This is the rule we recommend for kupid_get_notice_detail:
{
"version": "1",
"default": "deny",
"tools": {
"kupid_get_notice_detail": {}
}
}kupid_get_notice_detail is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
KUPID 공지사항의 상세 내용을 조회합니다. It is categorised as a Read tool in the Ku Portal MCP Server, which means it retrieves data without modifying state.
Register the Ku Portal MCP server in PolicyLayer and add a rule for kupid_get_notice_detail: 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 Ku Portal. Nothing to install.
kupid_get_notice_detail 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 kupid_get_notice_detail 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 kupid_get_notice_detail. 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.
kupid_get_notice_detail is provided by the Ku Portal MCP server (sonaiengine/ku-portal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ku Portal, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
31 Ku Portal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.