Return the effective application config. Secrets are masked unless include_secrets is true.
AI agents call get_config to retrieve information from Scifinder Route without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data and does not create, modify, delete, execute, or move resources. It is purely a query operation. Severity is low because configuration data typically contains non-sensitive or already-masked information. Confidence is high because the description unambiguously describes a read-only retrieval action.
From the tool's definition Tool name 'get_config' and description 'Return the effective application config' indicate a retrieval operation with no state modification. The note about secrets being 'masked unless include_secrets is true' shows the tool is read-only and defensive.
Attacks that exploit this kind of access
Return the effective application config. Secrets are masked unless include_secrets is true. It is categorised as a Read tool in the Scifinder Route MCP Server, which means it retrieves data without modifying state.
Register the Scifinder Route MCP server in PolicyLayer and add a rule for get_config: 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 Scifinder Route. Nothing to install.
get_config 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_config 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_config. 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_config is provided by the Scifinder Route MCP server (kettly1260/scifinder-route-mcp). 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 →