New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

aasagenticawesomeskills__search_skills

Retrieve matching skills from the verified local AAS catalog in stable catalog order, without relevance scores, ranking, recommendations, or local-state changes. Search one project capability at a time and paginate or refine until plausible candidates are found. matchMode any preserves broad toke...

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc
Low RISK CLASS
Category Read
Parameters 70 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/aasagenticawesomeskills--search-skills.md

What aasagenticawesomeskills__search_skills does on Rokha

AI agents call aasagenticawesomeskills__search_skills to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
tags array —
limit integer —
query string —
cursor integer —
matchMode string —
categories array —
requiredTerms array —

Parameters from the server's own tool schema.

Why aasagenticawesomeskills__search_skills is rated Low

Queries and retrieves skill registry data without creating, modifying, or deleting anything.

From the tool's definition Retrieve matching skills from verified local catalog; no side effects, state changes, or modifications.

Risk signalsBulk/mass operation — affects multiple targets

Questions about aasagenticawesomeskills__search_skills

What does the aasagenticawesomeskills__search_skills tool do? +

Retrieve matching skills from the verified local AAS catalog in stable catalog order, without relevance scores, ranking, recommendations, or local-state changes. Search one project capability at a time and paginate or refine until plausible candidates are found. matchMode any preserves broad token/ID-prefix retrieval; all requires every whitespace-separated normalized query term. requiredTerms always requires each supplied token. Caller-supplied categories match any normalized category; tags require every tag. Omit filters and query to reach the complete catalog. Results explain matched terms without choosing skills. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does aasagenticawesomeskills__search_skills accept? +

aasagenticawesomeskills__search_skills accepts 7 parameters: tags, limit, query, cursor, matchMode, categories, requiredTerms. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on aasagenticawesomeskills__search_skills? +

Register the Rokha MCP server in PolicyLayer and add a rule for aasagenticawesomeskills__search_skills: 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 Rokha. Nothing to install.

What risk level is aasagenticawesomeskills__search_skills? +

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

Can I rate-limit aasagenticawesomeskills__search_skills? +

Yes. Add a rate_limit block to the aasagenticawesomeskills__search_skills 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 aasagenticawesomeskills__search_skills completely? +

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

aasagenticawesomeskills__search_skills is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Rokha, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Rokha's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.