List all available data sources.
AI agents call list_available_sources to retrieve information from Academic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays information about available academic databases without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that returns metadata about data sources. Severity is low as misuse poses minimal risk—an agent could only enumerate sources, not access sensitive data or perform harmful actions.
From the tool's definition Tool is named 'list_available_sources' and described as listing available data sources. This is a query/enumeration operation with no side effects.
Attacks that exploit this kind of access
List all available data sources. It is categorised as a Read tool in the Academic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Academic MCP Server MCP server in PolicyLayer and add a rule for list_available_sources: 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 Academic MCP Server. Nothing to install.
list_available_sources 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 list_available_sources 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 list_available_sources. 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.
list_available_sources is provided by the Academic MCP Server MCP server (nanyang12138/academic-mcp-server). 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 →