fbiwanted.persons.recent

Get the most recently published FBI wanted posters, newest first, optionally restricted to one FBI field office. Useful for monitoring newly added subjects (api.fbi.gov, public US Government data)

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fbiwanted.persons.recent.md

WHAT IT DOES

What fbiwanted.persons.recent does on Apibase

AI agents call fbiwanted.persons.recent to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`page_size`	integer	—	Number of most recently published entries to return (default 20, max 50).
`field_office`	string	—	Restrict to a specific FBI field office slug (e.g. "seattle", "miami", "losangeles").

Parameters from the server's own tool schema.

RISK

Why fbiwanted.persons.recent is rated Low

Queries public FBI data without modifying, deleting, or executing code; pure information retrieval with no side effects.

From the tool's definition Get the most recently published FBI wanted posters, newest first, optional field office filter.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fbiwanted.persons.recent safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fbiwanted.persons.recent, this is the rule to start with:

fbiwanted.persons.recent Allowed

fbiwanted.persons.recent 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": {
    "fbiwanted.persons.recent": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every fbiwanted.persons.recent call is checked against it from then on.

FAQ

Questions about fbiwanted.persons.recent

What does the fbiwanted.persons.recent tool do? +

Get the most recently published FBI wanted posters, newest first, optionally restricted to one FBI field office. Useful for monitoring newly added subjects (api.fbi.gov, public US Government data). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does fbiwanted.persons.recent accept? +

fbiwanted.persons.recent accepts 2 parameters: page_size, field_office. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fbiwanted.persons.recent? +

Register the Apibase MCP server in PolicyLayer and add a rule for fbiwanted.persons.recent: 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 Apibase. Nothing to install.

What risk level is fbiwanted.persons.recent? +

fbiwanted.persons.recent is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fbiwanted.persons.recent? +

Yes. Add a rate_limit block to the fbiwanted.persons.recent 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 fbiwanted.persons.recent completely? +

Set action: deny in the PolicyLayer policy for fbiwanted.persons.recent. 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 fbiwanted.persons.recent? +

fbiwanted.persons.recent is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

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