gem-outdated

Lists outdated Ruby gems showing current and latest available versions.

SERVERDocker SOURCE@paretools/docker

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-docker/gem-outdated.md

WHAT IT DOES

What gem-outdated does on Docker

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

RISK

Why gem-outdated is rated Low

This tool performs a passive query of gem metadata to display version information. It has no side effects, does not create, modify, delete, or execute anything. The blast radius of misuse is minimal — at worst, an AI agent could spam version checks or gather information about the dependency landscape, but cannot cause harm to systems or data.

From the tool's definition Tool description explicitly states it 'Lists outdated Ruby gems' — a read-only information retrieval operation that queries gem version metadata without modifying any gems or system state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gem-outdated safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gem-outdated, this is the rule to start with:

gem-outdated Allowed

gem-outdated is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gem-outdated": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docker, apply this rule, and every gem-outdated call is checked against it from then on.

FAQ

Questions about gem-outdated

What does the gem-outdated tool do? +

Lists outdated Ruby gems showing current and latest available versions. It is categorised as a Read tool in the Docker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gem-outdated? +

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

What risk level is gem-outdated? +

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

Can I rate-limit gem-outdated? +

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

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

gem-outdated is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docker, and thousands of servers like it.

This server

All 202 Docker tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →