Get the detailed security vetting report for a skill (poll by job_id, claim_token supported). / 보안 검수 결과 상세 조회. 업로드 응답의 vetting_job_id 로 검수 결과를 폴링합니다. 에이전트가 이메일 없이 HTTP만으로 최종 결과를 받는 공식 권장 경로. ▶ 인증 (둘 중 하나): - api_key: 회원 계정의 API 키 (upload_skill 경로 업로더) - claim_token: Draft Upload(upload_skill_dra...
Risk signalsHandles credentials or secrets (api_key)
Part of the AI Skill Store server.
Free to start. No card required.
AI agents call get_vetting_result 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 get_vetting_result 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.
{
"version": "1",
"default": "deny",
"tools": {
"get_vetting_result": {}
}
}See the full AI Skill Store policy for all 18 tools.
These attack patterns abuse exactly the kind of access get_vetting_result gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get the detailed security vetting report for a skill (poll by job_id, claim_token supported). / 보안 검수 결과 상세 조회. 업로드 응답의 vetting_job_id 로 검수 결과를 폴링합니다. 에이전트가 이메일 없이 HTTP만으로 최종 결과를 받는 공식 권장 경로. ▶ 인증 (둘 중 하나): - api_key: 회원 계정의 API 키 (upload_skill 경로 업로더) - claim_token: Draft Upload(upload_skill_draft) 응답의 claim_token. API 키 없는 에이전트는 이 토큰으로 자신의 검수 결과를 폴링 가능. 반환 메시지에는 is_done 플래그, vetting_status, findings[] 가 포함됩니다. is_done=false 면 몇 초 후 다시 호출하세요 (보통 검수는 수 초~수십 초 소요). Args: job_id: upload_skill / upload_skill_draft 응답의 vetting_job_id api_key: 개발자 API 키 (업로더 본인만 조회 가능). 없으면 claim_token 필수. claim_token: Draft Upload 응답의 claim_token (api_key 대안). Returns: 검수 결과 메시지 (is_done 여부 + 결과 포함). It is categorised as a Read tool in the AI Skill Store MCP Server, which means it retrieves data without modifying state.
Register the AI Skill Store MCP server in PolicyLayer and add a rule for get_vetting_result: 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 AI Skill Store. Nothing to install.
get_vetting_result 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 get_vetting_result 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 get_vetting_result. 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.
get_vetting_result is provided by the AI Skill Store MCP server (garasegae/aiskillstore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 AI Skill Store tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.