Low Risk

pety_search_person

공직자 이름으로 재산공개 대상자를 검색합니다. DocumentCloud에 업로드된 관보 원본 전문 검색을 사용합니다. 동명이인이 여러 기관에 있을 수 있으며, 검색 결과에서 소속 기관과 직위를 확인하세요. 상세 재산 내역은 pety_get_asset_detail 도구에 document_id와 pages를 전달하여 조회합니다. Args: - name (string): 공직자 이름 (최소 2자) - year (string, optional): 연도 (미지정 시 최신) - format ('markdown' | 'jso...

Part of the Public Official MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call pety_search_person to retrieve information from Public Official without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though pety_search_person only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

public-official.yaml
tools:
  pety_search_person:
    rules:
      - action: allow

See the full Public Official policy for all 4 tools.

Tool Name pety_search_person
Category Read
Risk Level Low

Agents calling read-class tools like pety_search_person have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the pety_search_person tool do? +

공직자 이름으로 재산공개 대상자를 검색합니다. DocumentCloud에 업로드된 관보 원본 전문 검색을 사용합니다. 동명이인이 여러 기관에 있을 수 있으며, 검색 결과에서 소속 기관과 직위를 확인하세요. 상세 재산 내역은 pety_get_asset_detail 도구에 document_id와 pages를 전달하여 조회합니다. Args: - name (string): 공직자 이름 (최소 2자) - year (string, optional): 연도 (미지정 시 최신) - format ('markdown' | 'json'): 출력 형식 Returns: 검색된 인물 목록 (이름, 소속, 직위, 관보 문서 ID, 페이지 번호). It is categorised as a Read tool in the Public Official MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pety_search_person? +

Add a rule in your Intercept YAML policy under the tools section for pety_search_person. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Public Official MCP server.

What risk level is pety_search_person? +

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

Can I rate-limit pety_search_person? +

Yes. Add a rate_limit block to the pety_search_person rule in your Intercept 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 pety_search_person completely? +

Set action: deny in the Intercept policy for pety_search_person. 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 pety_search_person? +

pety_search_person is provided by the Public Official MCP server (public-official-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Public Official

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.