Skip to main content
Glama
Sign In
KubeCraft MCP Server

KubeCraft MCP Server

by cloudcrafttech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Inspect RBAC

inspect_rbac

Identify risky ClusterRole and Role rules including wildcards and escalate/bind/impersonate permissions, and view sample ClusterRoleBindings.

Instructions

Read-only RBAC review: heuristics for risky ClusterRole/Role rules (wildcards, escalate/bind/impersonate) and a sample of ClusterRoleBindings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_rbac"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoIf set, limit risky Role scanning to this namespace; ClusterRoles are always scanned cluster-wide

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description carries full burden. It declares read-only nature and heuristic approach, which is good. However, it does not mention permission requirements, output format, or that bindings are a sample (not exhaustive).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys key information. It is not verbose and front-loads the read-only nature and purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should clarify return format. It mentions 'sample of ClusterRoleBindings' but omits details about Role/ClusterRole findings. For a moderate-complexity tool, this is adequate but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear description for the `namespace` parameter. The tool description adds context that Roles are limited only if namespace is set, which aligns with the schema. Baseline 3 is appropriate as little additional value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it performs a read-only RBAC review, specifically targeting risky ClusterRole/Role rules and a sample of ClusterRoleBindings. This distinguishes it from sibling tools, none of which focus on RBAC auditing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for security reviews but does not explicitly state when to use versus alternatives. No sibling tool duplicates RBAC functionality, so guidance is adequate but could be more direct.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools