secret_get_names

List stored secret NAMES (never values).

Server LocalAnt yuga-hashimoto/localant
Category Read
Risk class Low
Parameters 00 required

What secret_get_names does on LocalAnt

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

Why secret_get_names needs a policy

This tool performs a read-only query to enumerate secret identifiers. While enumeration of secrets could assist an attacker in targeting specific credentials, the tool does not retrieve the actual secret values and causes no data modification or destruction.

From the tool's definition Tool is explicitly described as 'List stored secret NAMES (never values)' — a retrieval operation that queries metadata about secrets without exposing the secret values themselves.

Questions about secret_get_names

What does the secret_get_names tool do? +

List stored secret NAMES (never values). It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on secret_get_names? +

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

What risk level is secret_get_names? +

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

Can I rate-limit secret_get_names? +

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

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

secret_get_names is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.