fedreg-list-executive-orders
List Executive Orders from the Federal Register, optionally filtered by president.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/fedreg-list-executive-orders.md
What fedreg-list-executive-orders does on Meta Data Mcp
AI agents call fedreg-list-executive-orders 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.
Why fedreg-list-executive-orders is rated Low
This tool retrieves and queries publicly available Executive Order data from the Federal Register without creating, modifying, deleting, or executing any actions. It has no side effects beyond data retrieval. The blast radius of misuse is minimal — an agent could only retrieve more or different Executive Orders than intended, which poses no security, financial, or operational risk.
From the tool's definition Tool name contains 'list' (retrieve operation) and description states 'List Executive Orders' — a query operation with no modification, deletion, or execution capability. The filtering by president is a standard read parameter.
Attacks that exploit this kind of access
The rule that runs fedreg-list-executive-orders 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 fedreg-list-executive-orders, this is the rule to start with:
fedreg-list-executive-orders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every fedreg-list-executive-orders call is checked against it from then on.
Questions about fedreg-list-executive-orders
List Executive Orders from the Federal Register, optionally filtered by president. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for fedreg-list-executive-orders: 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.
fedreg-list-executive-orders 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 fedreg-list-executive-orders 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 fedreg-list-executive-orders. 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.
fedreg-list-executive-orders 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.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue