get_certificate_authority
Get the certificate authority for a Memorystore for Valkey instance.
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
Attacks that exploit this kind of access
The rule that runs get_certificate_authority safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_certificate_authority, this is the rule to start with:
get_certificate_authority is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every get_certificate_authority call is checked against it from then on.
Questions about get_certificate_authority
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.
get_certificate_authority accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
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.
get_certificate_authority 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_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.
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.
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
Across the catalogue