get_pods

List pods in namespace

SERVERNcp SOURCE@portel/ncp

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-portel-dev-ncp/get-pods.md

WHAT IT DOES

What get_pods does on Ncp

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

RISK

Why get_pods is rated Low

This is a straightforward list/query operation that retrieves pod information from a Kubernetes cluster. It has no side effects, performs no modifications, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an agent could discover pod details but cannot create, modify, delete, or execute actions on them. This is clearly a Read category tool.

From the tool's definition Tool name 'get_pods' and description 'List pods in namespace' indicate a read-only operation that queries and returns information about Kubernetes pods without modifying any state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_pods safely

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

get_pods Allowed

get_pods 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": {
    "get_pods": {}
  }
}

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

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

FAQ

Questions about get_pods

What does the get_pods tool do? +

List pods in namespace. It is categorised as a Read tool in the Ncp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pods? +

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

What risk level is get_pods? +

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

Can I rate-limit get_pods? +

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

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

get_pods is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ncp, and thousands of servers like it.

This server

All 275 Ncp tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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