List all information requests associated with the firm.
AI agents call list_information_requests to retrieve information from Standard Metrics 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 enumerates existing information requests without creating, modifying, deleting, or executing any operations. It is a straightforward query operation against portfolio/firm data. Severity is low because listing requests poses minimal risk even if misused by an agent — it exposes existing data but cannot alter state or trigger external actions.
From the tool's definition Tool name contains 'list' and description states it 'List[s] all information requests' — a pure data retrieval operation with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access list_information_requests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Standard Metrics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_information_requests:
{
"version": "1",
"default": "deny",
"tools": {
"list_information_requests": {}
}
}list_information_requests 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 information requests associated with the firm. It is categorised as a Read tool in the Standard Metrics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Standard Metrics MCP Server MCP server in PolicyLayer and add a rule for list_information_requests: 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 Standard Metrics MCP Server. Nothing to install.
list_information_requests 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_information_requests 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_information_requests. 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_information_requests is provided by the Standard Metrics MCP Server MCP server (quaestor-technologies/smx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Standard Metrics 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.
19 Standard Metrics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.