List all configured database connections (names and types only, credentials are not shown). Use describe_datasource for connection details and status.
AI agents call list_datasources to retrieve information from SLayer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about configured datasources—names and types only—without modifying, executing queries, deleting resources, or affecting financial systems. It is a simple enumeration operation with no destructive or operational consequences. The explicit note that credentials are not shown further confirms this is a safe read operation.
From the tool's definition Tool name 'list_datasources' and description 'List all configured database connections (names and types only, credentials are not shown)' indicate retrieval without side effects.
Documented attack patterns abuse exactly the kind of access list_datasources gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SLayer, and nothing reaches the server without passing your rules. This is the rule we recommend for list_datasources:
{
"version": "1",
"default": "deny",
"tools": {
"list_datasources": {}
}
}list_datasources is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all configured database connections (names and types only, credentials are not shown). Use describe_datasource for connection details and status. It is categorised as a Read tool in the SLayer MCP Server, which means it retrieves data without modifying state.
Register the SLayer MCP server in PolicyLayer and add a rule for list_datasources: 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 SLayer. Nothing to install.
list_datasources 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_datasources 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_datasources. 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_datasources is provided by the SLayer MCP server (motleyai/slayer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SLayer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 SLayer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.