Low Risk

pdb_get_polymer_entity

pdb_get_polymer_entity

How to control pdb_get_polymer_entity ↓

What pdb_get_polymer_entity does on OrigeneMCP

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

Low Risk

Why pdb_get_polymer_entity needs a policy

This tool retrieves polymer entity information (likely protein structures or sequences) from PDB, a public database. No description is available, but the naming pattern and context of sibling retrieval tools strongly indicate read-only data access with no side effects. The blast radius is low since it only returns information without modifying data or triggering external operations.

From the tool's definition Tool name 'pdb_get_polymer_entity' indicates retrieval from the Protein Data Bank (PDB). The 'get_' prefix and 'polymer_entity' object suggest querying/fetching structural data.

Documented attack patterns abuse exactly the kind of access pdb_get_polymer_entity gives an agent:

How to control pdb_get_polymer_entity

PolicyLayer is an MCP gateway — it sits between your AI agents and OrigeneMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for pdb_get_polymer_entity:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pdb_get_polymer_entity": {}
  }
}

pdb_get_polymer_entity is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OrigeneMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about pdb_get_polymer_entity

What does the pdb_get_polymer_entity tool do? +

pdb_get_polymer_entity. It is categorised as a Read tool in the OrigeneMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pdb_get_polymer_entity? +

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

What risk level is pdb_get_polymer_entity? +

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

Can I rate-limit pdb_get_polymer_entity? +

Yes. Add a rate_limit block to the pdb_get_polymer_entity 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 pdb_get_polymer_entity completely? +

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

pdb_get_polymer_entity is provided by the Origene MCP server (gentel-lab/origenemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OrigeneMCP tool call.

Start from OrigeneMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

439 OrigeneMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.