Alias for bootstrap — returns targets, skills, webhooks, memories, wiki pages, and vaults.
AI agents call discover 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.
The tool retrieves information about system configuration (targets, skills, webhooks, memories, wiki pages, vaults). While this is informational only, the sensitivity is elevated to medium severity because discovering system architecture, credentials storage mechanisms (vaults), and integration points (webhooks, targets) could enable follow-on attacks.
From the tool's definition Tool description states it 'returns targets, skills, webhooks, memories, wiki pages, and vaults' — all retrieval/query operations with no modification or execution semantics. Named as an alias for 'bootstrap' which enumerates available resources.
Documented attack patterns abuse exactly the kind of access discover gives an agent:
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 discover:
{
"version": "1",
"default": "deny",
"tools": {
"discover": {}
}
} discover is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Alias for bootstrap — returns targets, skills, webhooks, memories, wiki pages, and vaults. It is categorised as a Read tool in the Shellgate MCP Server, which means it retrieves data without modifying state.
Register the Shellgate MCP server in PolicyLayer and add a rule for discover: 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.
discover 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 discover 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 discover. 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.
discover 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.
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.