New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_certificate_authority

Get the certificate authority for a Memorystore for Valkey instance.

SERVERMcp SOURCEhttps://memorystore.googleapis.com/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-memorystore-mcp/get-certificate-authority.md

What get_certificate_authority does on Mcp

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

ParameterTypeRequiredDescription
name string Yes Required. The name of the certificate authority. Format: projects/{project}/locations/{location}/instances/{instance}/certificateAuthority

Parameters from the server's own tool schema.

Why get_certificate_authority is rated Low

This tool retrieves certificate authority information, which is a read-only query operation. It does not modify, delete, execute, or move any resources. The blast radius is minimal as it only exposes certificate metadata needed for secure connections. Confidence is high because the verb 'get' and 'retrieve' semantics are unambiguous.

From the tool's definition Tool name 'get_certificate_authority' and description 'Get the certificate authority for a Memorystore for Valkey instance' indicate a retrieval operation with no side effects.

Questions about get_certificate_authority

What does the get_certificate_authority tool do? +

Get the certificate authority for a Memorystore for Valkey instance. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_certificate_authority accept? +

get_certificate_authority accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_certificate_authority? +

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

What risk level is get_certificate_authority? +

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

Can I rate-limit get_certificate_authority? +

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

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

get_certificate_authority is provided by the MCP server (https://memorystore.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on , and thousands of servers like it.

This server

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

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.