Scan a text for DOIs and citations, validating them and identifying missing DOIs.
AI agents call audit_manuscript to retrieve information from BioCite-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes metadata about citations within a manuscript but does not create, modify, delete, or execute code. It performs passive auditing—comparing existing citations against reference databases. No side effects or state changes occur to the manuscript or external systems. This is purely a Read operation with minimal security risk.
From the tool's definition The tool 'audit_manuscript' scans text for DOIs and citations, validating them and identifying missing DOIs. The verbs 'scan' and 'validating' indicate information retrieval and analysis with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Scan a text for DOIs and citations, validating them and identifying missing DOIs. It is categorised as a Read tool in the BioCite-MCP MCP Server, which means it retrieves data without modifying state.
Register the BioCite- MCP server in PolicyLayer and add a rule for audit_manuscript: 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 BioCite-MCP. Nothing to install.
audit_manuscript 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 audit_manuscript 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 audit_manuscript. 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.
audit_manuscript is provided by the BioCite- MCP server (muslus/biocite-mcp). 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 →