Low Risk

kupid_dept_notice_detail

학과/대학원 공지사항의 상세 내용을 조회합니다 (인증 불필요).

How to control kupid_dept_notice_detail ↓

What kupid_dept_notice_detail does on Ku Portal

AI agents call kupid_dept_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.

Low Risk

Why kupid_dept_notice_detail needs a policy

This tool retrieves detailed content from department/graduate school notices. The action is purely informational—it queries and returns data without modifying, creating, deleting, or executing anything. The public nature (no authentication required) and read-only semantics place it squarely in the Read category with low severity.

From the tool's definition Tool name includes 'detail' and description states '조회합니다' (retrieve/query). The phrase '(인증 불필요)' (authentication not required) indicates public data retrieval with no side effects.

Documented attack patterns abuse exactly the kind of access kupid_dept_notice_detail gives an agent:

How to control kupid_dept_notice_detail

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_dept_notice_detail:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "kupid_dept_notice_detail": {}
  }
}

kupid_dept_notice_detail is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Ku Portal — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about kupid_dept_notice_detail

What does the kupid_dept_notice_detail tool do? +

학과/대학원 공지사항의 상세 내용을 조회합니다 (인증 불필요). It is categorised as a Read tool in the Ku Portal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on kupid_dept_notice_detail? +

Register the Ku Portal MCP server in PolicyLayer and add a rule for kupid_dept_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.

What risk level is kupid_dept_notice_detail? +

kupid_dept_notice_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit kupid_dept_notice_detail? +

Yes. Add a rate_limit block to the kupid_dept_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.

How do I block kupid_dept_notice_detail completely? +

Set action: deny in the PolicyLayer policy for kupid_dept_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.

What MCP server provides kupid_dept_notice_detail? +

kupid_dept_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.

Enforce policy on every Ku Portal tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.