List analyses produced from a study.
AI agents call mgnify_study_analyses to retrieve information from MGnify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about analyses associated with a study from the MGnify API. It performs a data query operation with no capacity to modify, delete, or execute arbitrary code. The blast radius is minimal—misuse would only expose existing scientific data that is typically already public or intended for research access.
From the tool's definition Tool name 'mgnify_study_analyses' and description 'List analyses produced from a study' indicate a retrieval/query operation with no side effects. The verb 'list' is a classic read operation that queries and returns data without modification.
Attacks that exploit this kind of access
List analyses produced from a study. It is categorised as a Read tool in the MGnify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MGnify MCP Server MCP server in PolicyLayer and add a rule for mgnify_study_analyses: 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 MGnify MCP Server. Nothing to install.
mgnify_study_analyses 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 mgnify_study_analyses 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 mgnify_study_analyses. 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.
mgnify_study_analyses is provided by the MGnify MCP Server MCP server (mgs-sails/mgnify-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 →