search_author
AI agents call search_author 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.
This tool retrieves author information from Scopus—a read-only operation with no side effects. Even if misused, it cannot modify, delete, or execute code. The main risk is information disclosure or API quota exhaustion, both low-severity. Confidence is moderate-to-high due to empty description, but context strongly suggests a benign search operation.
From the tool's definition Tool name 'search_author' in a literature discovery context (Scopus), alongside sibling tools like 'get_author_profile', 'find_experts_in', and 'advanced_search'.
Attacks that exploit this kind of access
search_author. 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 search_author: 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.
search_author 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 search_author 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 search_author. 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.
search_author 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 →