treasury-list-endpoints

List the curated set of US Treasury Fiscal Data endpoints supported by this provider.

SERVERMeta Data Mcp SOURCEpypi:meta-data-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/treasury-list-endpoints.md

WHAT IT DOES

What treasury-list-endpoints does on Meta Data Mcp

AI agents call treasury-list-endpoints to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why treasury-list-endpoints is rated Low

This tool lists available endpoints from the US Treasury Fiscal Data API—a pure information retrieval operation with no side effects, no code execution, and no ability to modify or destroy data. It is a metadata discovery function, making it clearly a Read category tool with low severity.

From the tool's definition Tool name 'treasury-list-endpoints' and description 'List the curated set of US Treasury Fiscal Data endpoints' indicate a retrieval/query operation with no data modification, deletion, or execution of arbitrary operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs treasury-list-endpoints safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For treasury-list-endpoints, this is the rule to start with:

treasury-list-endpoints Allowed

treasury-list-endpoints is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "treasury-list-endpoints": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every treasury-list-endpoints call is checked against it from then on.

FAQ

Questions about treasury-list-endpoints

What does the treasury-list-endpoints tool do? +

List the curated set of US Treasury Fiscal Data endpoints supported by this provider. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on treasury-list-endpoints? +

Register the Meta Data MCP server in PolicyLayer and add a rule for treasury-list-endpoints: 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 Meta Data Mcp. Nothing to install.

What risk level is treasury-list-endpoints? +

treasury-list-endpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit treasury-list-endpoints? +

Yes. Add a rate_limit block to the treasury-list-endpoints 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.

How do I block treasury-list-endpoints completely? +

Set action: deny in the PolicyLayer policy for treasury-list-endpoints. 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.

What MCP server provides treasury-list-endpoints? +

treasury-list-endpoints is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →