Low Risk

org_skill_read

Read the full content of a shared organization skill from Shellgate

How to control org_skill_read ↓

What org_skill_read does on Shellgate

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

Low Risk

Why org_skill_read needs a policy

This is a data retrieval operation (Read category). However, severity is elevated to medium rather than low because: (1) it accesses 'shared organization skill' content, suggesting potentially sensitive organizational intellectual property, workflows, or configurations; (2) in the context of Shellgate (a gateway for AI agents with credential injection and SSH access), reading shared skills could expose patterns that…

From the tool's definition Tool name contains 'read' and description explicitly states 'Read the full content' with no indication of modification, deletion, or execution. The action is retrieving/querying data from a shared organization skill.

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

How to control org_skill_read

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

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

org_skill_read 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 Shellgate — 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 org_skill_read

What does the org_skill_read tool do? +

Read the full content of a shared organization skill from Shellgate. It is categorised as a Read tool in the Shellgate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on org_skill_read? +

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

What risk level is org_skill_read? +

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

Can I rate-limit org_skill_read? +

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

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

org_skill_read is provided by the Shellgate MCP server (matthiastjong/shellgate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Shellgate tool call.

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

31 Shellgate 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.