get_card
Retrieve full details for a Huly card including markdown content. Use this to view card content and metadata.
This record as markdown: /tools/dugynoo-huly-mcp/get-card.md
What get_card does on Huly
AI agents call get_card to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_card is rated Low
This tool performs a query operation to fetch and display existing card data without creating, modifying, deleting, or executing any external operations. It has no destructive or financial implications. The low severity reflects minimal blast radius if misused—an agent could only over-retrieve data, causing potential information disclosure but no operational harm.
From the tool's definition Tool name is 'get_card' and description states 'Retrieve full details for a Huly card including markdown content. Use this to view card content and metadata.' The verbs 'Retrieve' and 'view' indicate read-only operations with no side effects.
Attacks that exploit this kind of access
The rule that runs get_card safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_card, this is the rule to start with:
get_card 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 Huly, apply this rule, and every get_card call is checked against it from then on.
Questions about get_card
Retrieve full details for a Huly card including markdown content. Use this to view card content and metadata. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly 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 Huly. Nothing to install.
get_card 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_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.
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.
get_card is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue