get_string_ids

Map protein names, synonyms, and UniProt identifiers to STRING identifiers. Species parameter uses NCBI taxon IDs (e.g., 9606 for human, 10090 for mouse).

Server STRING MCP Server munch-group/string-mcp
Category Read
Risk class Low
Parameters 00 required

What get_string_ids does on STRING MCP Server

AI agents call get_string_ids to retrieve information from STRING MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_string_ids needs a policy

This is a straightforward lookup/query operation that retrieves protein identifier mappings from the STRING database. It has no side effects—it only reads and returns existing data in a different identifier format. No data is created, modified, deleted, or financial obligations incurred. The blast radius of misuse is minimal since the tool cannot alter any data or trigger external operations.

From the tool's definition Tool maps/resolves protein identifiers to STRING IDs with no modification capability. Description states it enables 'mapping identifiers' and 'retrieving' data, with no language indicating data creation, modification, deletion, or external state changes.

Questions about get_string_ids

What does the get_string_ids tool do? +

Map protein names, synonyms, and UniProt identifiers to STRING identifiers. Species parameter uses NCBI taxon IDs (e.g., 9606 for human, 10090 for mouse). It is categorised as a Read tool in the STRING MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_string_ids? +

Register the STRING MCP Server MCP server in PolicyLayer and add a rule for get_string_ids: 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 STRING MCP Server. Nothing to install.

What risk level is get_string_ids? +

get_string_ids is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_string_ids? +

Yes. Add a rate_limit block to the get_string_ids 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.

How do I block get_string_ids completely? +

Set action: deny in the PolicyLayer policy for get_string_ids. 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.

What MCP server provides get_string_ids? +

get_string_ids is provided by the STRING MCP Server MCP server (munch-group/string-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.