Returns answers to frequently asked questions about clinical trials.
AI agents call get_faq to retrieve information from Cardiovascular Disease without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static or pre-compiled FAQ content about clinical trials. It performs a simple data query operation without creating, modifying, deleting, or executing any code. The function is purely informational and has no capability to alter system state, financial impact, or trigger external operations. This is clearly a Read category tool with low severity risk.
From the tool's definition Tool name 'get_faq' and description 'Returns answers to frequently asked questions' indicate a retrieval operation with no side effects or data modification.
Attacks that exploit this kind of access
Returns answers to frequently asked questions about clinical trials. It is categorised as a Read tool in the Cardiovascular Disease MCP Server, which means it retrieves data without modifying state.
Register the Cardiovascular Disease MCP server in PolicyLayer and add a rule for get_faq: 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 Cardiovascular Disease. Nothing to install.
get_faq 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_faq 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_faq. 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_faq is provided by the Cardiovascular Disease MCP server (jamesvdinh/cardiovascular-disease-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →