List available example datasets for testing SPIRED-Stab predictions.
AI agents call list_example_data to retrieve information from SPIRED-Stab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates available example data for testing purposes. It has no side effects, does not modify data, execute code, or trigger external operations. It is a straightforward read operation with minimal risk even if misused, as it only exposes metadata about pre-existing test datasets.
From the tool's definition Tool name 'list_example_data' and description 'List available example datasets' indicate retrieval of metadata about example datasets with no modification, deletion, or execution of operations.
Attacks that exploit this kind of access
List available example datasets for testing SPIRED-Stab predictions. It is categorised as a Read tool in the SPIRED-Stab MCP MCP Server, which means it retrieves data without modifying state.
Register the SPIRED-Stab MCP server in PolicyLayer and add a rule for list_example_data: 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 SPIRED-Stab MCP. Nothing to install.
list_example_data 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_example_data 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_example_data. 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_example_data is provided by the SPIRED-Stab MCP server (macromnex/spired_stab_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 →