get_document_details
AI agents call get_document_details to retrieve information from Strato Scopus MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves document details from Scopus—a literature discovery operation with no side effects, reversible modifications, or destructive capability. The empty description weakens confidence slightly, but the naming convention and server context (literature discovery) clearly indicate a query operation.
From the tool's definition Tool name 'get_document_details' is a getter for document metadata. The sibling tools include read-only operations like 'get_author_profile', 'get_citation_metrics', and 'explore_topic', establishing a pattern of retrieval-focused functionality on this Scopus…
Attacks that exploit this kind of access
get_document_details. It is categorised as a Read tool in the Strato Scopus MCP MCP Server, which means it retrieves data without modifying state.
Register the Strato Scopus MCP server in PolicyLayer and add a rule for get_document_details: 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 Strato Scopus MCP. Nothing to install.
get_document_details 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 get_document_details 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 get_document_details. 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.
get_document_details is provided by the Strato Scopus MCP server (stratosphereips/strato-mcp-scopus). 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 →