Return the configured datasource priority list (most-preferred
AI agents call get_datasource_priority 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 queries and returns existing configuration (datasource priority ordering) without creating, modifying, deleting, or executing any operations. It is a read-only retrieval operation with minimal security impact—an agent misusing it would at worst learn which datasources are preferred, which is unlikely to cause harm.
From the tool's definition Tool name 'get_datasource_priority' and description 'Return the configured datasource priority list' indicate retrieval of configuration data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_datasource_priority 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 get_datasource_priority:
{
"version": "1",
"default": "deny",
"tools": {
"get_datasource_priority": {}
}
}get_datasource_priority 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.
Return the configured datasource priority list (most-preferred. 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 get_datasource_priority: 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.
get_datasource_priority 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_datasource_priority 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_datasource_priority. 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_datasource_priority 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.