get_card

get_card

Server Astrolabe zebrr/astrolabe-mcp
Category Read
Risk class Low
Parameters 00 required

What get_card does on Astrolabe

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

Why get_card needs a policy

The tool appears to retrieve a 'card' (likely a documentation card or metadata object) from the indexed projects. No evidence of data modification, deletion, or external execution. Categorized as Read with low severity due to the read-only nature and limited blast radius of document retrieval.

From the tool's definition Tool named 'get_card' on a documentation search/navigation server; sibling tools include 'read_doc', 'search_docs', 'list_docs', and 'get_doc_types', all retrieval operations.

Questions about get_card

What does the get_card tool do? +

get_card. It is categorised as a Read tool in the Astrolabe MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_card? +

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

What risk level is get_card? +

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

Can I rate-limit get_card? +

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

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

get_card is provided by the Astrolabe MCP server (zebrr/astrolabe-mcp). 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.