pdb-entry
Fetch 3D macromolecular structure metadata from RCSB PDB by entry ID.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/pdb-entry.md
What pdb-entry does on Meta Data Mcp
AI agents call pdb-entry to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pdb-entry is rated Low
This tool queries a public scientific database (RCSB PDB — Protein Data Bank) to retrieve existing structural metadata. There is no data creation, modification, deletion, code execution, or financial impact. The operation is a simple GET request against an open API. Even if misused, an AI agent can only retrieve data that is already publicly available, posing minimal risk.
From the tool's definition Tool name 'pdb-entry' and description 'Fetch 3D macromolecular structure metadata from RCSB PDB by entry ID' indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs pdb-entry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pdb-entry, this is the rule to start with:
pdb-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 Meta Data Mcp, apply this rule, and every pdb-entry call is checked against it from then on.
Questions about pdb-entry
Fetch 3D macromolecular structure metadata from RCSB PDB by entry ID. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for pdb-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 Meta Data Mcp. Nothing to install.
pdb-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 pdb-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 pdb-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.
pdb-entry is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue