get
AI agents call get to retrieve information from Mcp Uniprot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve protein data from UniProt without modifying, deleting, or executing operations. The empty description reduces confidence slightly, but the tool name 'get' combined with the server's stated purpose of 'retrieval' and sibling tools being search/query operations strongly suggests read-only data access. No financial, destructive, or execute-level risk is evident.
From the tool's definition Tool named 'get' on a knowledge base server (UniProt) that provides 'access to...protein entries' and 'retrieval of protein entries'. The name 'get' and server context (search, retrieval, knowledge base access) indicate data retrieval.
Attacks that exploit this kind of access
get. It is categorised as a Read tool in the Mcp Uniprot MCP Server, which means it retrieves data without modifying state.
Register the Mcp Uniprot MCP server in PolicyLayer and add a rule for get: 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 Mcp Uniprot. Nothing to install.
get 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 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. 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 is provided by the Mcp Uniprot MCP server (pipeworx-io/mcp-uniprot). 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 →