get_mesh_terms
AI agents call get_mesh_terms to retrieve information from PubMed Enhanced Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries MeSH term data with no side effects. It fits the Read category definition: retrieves data without modifying, deleting, or executing operations. The confidence is 0.85 rather than higher because the description is empty, leaving some ambiguity, but the tool name and server context strongly indicate a lookup function.
From the tool's definition Tool name 'get_mesh_terms' suggests retrieval of Medical Subject Headings (MeSH) terminology data from PubMed. Server context indicates 'MeSH term lookup' as an advanced feature, confirming this is a data retrieval operation.
Attacks that exploit this kind of access
get_mesh_terms. It is categorised as a Read tool in the PubMed Enhanced Search MCP Server, which means it retrieves data without modifying state.
Register the PubMed Enhanced Search MCP server in PolicyLayer and add a rule for get_mesh_terms: 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 PubMed Enhanced Search. Nothing to install.
get_mesh_terms 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_mesh_terms 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_mesh_terms. 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_mesh_terms is provided by the PubMed Enhanced Search MCP server (leescot/pubmed-mcp-smithery). 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 →