Get detailed explanation of how a grant opportunity was scored.
AI agents call explain_grant_score to retrieve information from Grants Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing scoring data to provide explanations to users. It has no side effects, does not create or modify data, does not execute code or commands, and does not delete or move money. It is purely informational, making it a Read category tool with low severity since misuse would only expose scoring logic without enabling harmful actions.
From the tool's definition The tool description states 'Get detailed explanation of how a grant opportunity was scored.' This is a retrieval operation that returns scoring methodology and explanations without modifying or executing any external operations.
Documented attack patterns abuse exactly the kind of access explain_grant_score gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Grants Search MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for explain_grant_score:
{
"version": "1",
"default": "deny",
"tools": {
"explain_grant_score": {}
}
}explain_grant_score 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.
Get detailed explanation of how a grant opportunity was scored. It is categorised as a Read tool in the Grants Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Grants Search MCP Server MCP server in PolicyLayer and add a rule for explain_grant_score: 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 Grants Search MCP Server. Nothing to install.
explain_grant_score 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 explain_grant_score 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 explain_grant_score. 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.
explain_grant_score is provided by the Grants Search MCP Server MCP server (tar-ive/grants-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Grants Search MCP Server, 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.
12 Grants Search MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.