list_sources

Get a list of all source libraries (RISM sigla) in the archive with record counts and location info

Server Digital Guitar Archive MCP Server rcoldwell/mcp
Category Read
Risk class Low
Parameters 00 required

What list_sources does on Digital Guitar Archive MCP Server

AI agents call list_sources to retrieve information from Digital Guitar Archive MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_sources needs a policy

This tool retrieves and lists informational metadata about source libraries (RISM sigla, record counts, location info) from a database. It performs a query operation with no ability to modify, delete, or execute arbitrary actions. The blast radius is minimal—misuse by an AI agent would only result in enumeration of available sources, with no data modification or external side effects possible.

From the tool's definition Tool name 'list_sources' and description 'Get a list of all source libraries' indicates retrieval of metadata without modification. Server description emphasizes 'search and retrieve records' with 'no side effects' consistent with Read operations.

Questions about list_sources

What does the list_sources tool do? +

Get a list of all source libraries (RISM sigla) in the archive with record counts and location info. It is categorised as a Read tool in the Digital Guitar Archive MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_sources? +

Register the Digital Guitar Archive MCP Server MCP server in PolicyLayer and add a rule for list_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 Digital Guitar Archive MCP Server. Nothing to install.

What risk level is list_sources? +

list_sources is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_sources? +

Yes. Add a rate_limit block to the list_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.

How do I block list_sources completely? +

Set action: deny in the PolicyLayer policy for list_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.

What MCP server provides list_sources? +

list_sources is provided by the Digital Guitar Archive MCP Server MCP server (rcoldwell/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

list_sources is one line of Digital Guitar Archive MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.