Low Risk

get_skill

get_skill

How to control get_skill ↓

What get_skill does on Loreto

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

Low Risk

Why get_skill needs a policy

With no description provided, confidence is reduced, but the tool name and surrounding tool context (list_skills, marketplace operations) indicate this is a query/retrieval operation with no side effects. It likely fetches skill metadata or details, making it a Read operation with low blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_skill' and context indicate data retrieval. Sibling tools include 'list_skills', 'marketplace_get_listing', and 'get_quota', which are clearly read operations.

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

How to control get_skill

PolicyLayer is an MCP gateway — it sits between your AI agents and Loreto, and nothing reaches the server without passing your rules. This is the rule we recommend for get_skill:

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

get_skill 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 Loreto — 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 get_skill

What does the get_skill tool do? +

get_skill. It is categorised as a Read tool in the Loreto MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_skill? +

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

What risk level is get_skill? +

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

Can I rate-limit get_skill? +

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

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

get_skill is provided by the Loreto MCP server (kopias/loreto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Loreto tool call.

Start from Loreto, 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.

13 Loreto 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.