업로드한 스킬의 보안 검수(vetting) 상태를 확인합니다. upload_skill 결과에서 받은 version_id와 API 키가 필요합니다. Args: version_id: 스킬 버전 ID (upload_skill 결과의 version_id 또는 vetting_job_id) api_key: 개발자 API 키 (스킬 소유자만 조회 가능) Returns: 검수 상태 메시지
Handles credentials or secrets (api_key)
Part of the AI Skill Store MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call check_vetting_status to retrieve information from AI Skill Store 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 check_vetting_status 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.
tools:
check_vetting_status:
rules:
- action: allowSee the full AI Skill Store policy for all 10 tools.
Agents calling read-class tools like check_vetting_status have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
업로드한 스킬의 보안 검수(vetting) 상태를 확인합니다. upload_skill 결과에서 받은 version_id와 API 키가 필요합니다. Args: version_id: 스킬 버전 ID (upload_skill 결과의 version_id 또는 vetting_job_id) api_key: 개발자 API 키 (스킬 소유자만 조회 가능) Returns: 검수 상태 메시지 . It is categorised as a Read tool in the AI Skill Store MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for check_vetting_status. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AI Skill Store MCP server.
check_vetting_status 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 check_vetting_status 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.
Set action: deny in the Intercept policy for check_vetting_status. 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.
check_vetting_status is provided by the AI Skill Store MCP server (garasegae/aiskillstore). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept