Namespace posture: pods, configmaps, secrets-meta (when enabled).
AI agents call get_namespace to retrieve information from Gke Cred Audit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about Kubernetes namespace resources (pods, configmaps, secrets-meta). It performs no modifications, deletions, or code execution. While the retrieval of secrets metadata could expose sensitive information structure, the core function is informational/read-only.
From the tool's definition Tool name 'get_namespace' and description 'Namespace posture: pods, configmaps, secrets-meta (when enabled)' indicates retrieval of metadata about namespace resources including pods, configmaps, and secrets metadata.
Attacks that exploit this kind of access
Namespace posture: pods, configmaps, secrets-meta (when enabled). It is categorised as a Read tool in the Gke Cred Audit MCP Server, which means it retrieves data without modifying state.
Register the Gke Cred Audit MCP server in PolicyLayer and add a rule for get_namespace: 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 Gke Cred Audit. Nothing to install.
get_namespace 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_namespace 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_namespace. 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_namespace is provided by the Gke Cred Audit MCP server (rrupesh/mcp-test). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →