science.uniprot.entry
Get full annotation details for a protein by UniProt accession number (e.g. P69905, P01308). Returns protein name, EC numbers, alternative names, organism and lineage, gene names, sequence (first 200 aa), molecular weight, biological function, subcellular location, associated diseases, keywords, ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/science.uniprot.entry.md
What science.uniprot.entry does on Apibase
AI agents call science.uniprot.entry to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
accession | string | Yes | UniProt accession number (e.g. "P69905" for hemoglobin alpha, "P01308" for insulin, "P53_HUMAN" entry name also accepted). Six or ten character alphanumeric cod |
Parameters from the server's own tool schema.
Why science.uniprot.entry is rated Low
Tool retrieves publicly available protein annotation data with no side effects or modifications.
From the tool's definition Get full annotation details for a protein by UniProt accession number. Returns protein name, sequence, function.
Attacks that exploit this kind of access
The rule that runs science.uniprot.entry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For science.uniprot.entry, this is the rule to start with:
science.uniprot.entry 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 Apibase, apply this rule, and every science.uniprot.entry call is checked against it from then on.
Questions about science.uniprot.entry
Get full annotation details for a protein by UniProt accession number (e.g. P69905, P01308). Returns protein name, EC numbers, alternative names, organism and lineage, gene names, sequence (first 200 aa), molecular weight, biological function, subcellular location, associated diseases, keywords, cross-references to PDB/Ensembl/RefSeq/OMIM/PubMed, and feature count. P69905 = hemoglobin alpha chain; P01308 = human insulin; P04637 = tumor suppressor p53 (TP53). CC BY 4.0 — Universal Protein Resource (UniProt Consortium). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
science.uniprot.entry accepts 1 parameter: accession. Required: accession. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for science.uniprot.entry: 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 Apibase. Nothing to install.
science.uniprot.entry 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 science.uniprot.entry 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 science.uniprot.entry. 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.
science.uniprot.entry is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue