Get the full tool detail for a tool name.
AI agents call get-tool to retrieve information from Nimble without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval operation that queries tool metadata. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. It is purely informational, fitting the Read category. Severity is low because even if misused, it only exposes tool descriptions and does not directly impact system state or data.
From the tool's definition Tool name is 'get-tool' and description states 'Get the full tool detail for a tool name' — this retrieves metadata about available tools without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access get-tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Nimble, and nothing reaches the server without passing your rules. This is the rule we recommend for get-tool:
{
"version": "1",
"default": "deny",
"tools": {
"get-tool": {}
}
}get-tool 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.
Get the full tool detail for a tool name. It is categorised as a Read tool in the Nimble MCP Server, which means it retrieves data without modifying state.
Register the Nimble MCP server in PolicyLayer and add a rule for get-tool: 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 Nimble. Nothing to install.
get-tool 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-tool 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-tool. 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-tool is provided by the Nimble MCP server (mquan/nimble). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Nimble, 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.
3 Nimble tools catalogued and risk-classified — across an index of 43,000+ MCP servers.