fbiwanted.persons.by_category
Browse FBI wanted posters by category: Ten Most Wanted Fugitives, Most Wanted Fraudsters, kidnappings, missing persons, seeking-information cases, Endangered Child Alert Program, or law-enforcement-assistance requests. Returns the same subject detail as fbiwanted.persons.search (api.fbi.gov)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fbiwanted.persons.by-category.md
What fbiwanted.persons.by_category does on Apibase
AI agents call fbiwanted.persons.by_category 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 | integer | — | Page number for pagination (default 1). |
category | string | Yes | Poster category: "ten" (Ten Most Wanted Fugitives), "fraudster" (Most Wanted Fraudsters), "kidnapping", "missing" (missing persons), "information" (seeking info |
page_size | integer | — | Results per page (default 20, max 50). |
Parameters from the server's own tool schema.
Why fbiwanted.persons.by_category is rated Low
Tool queries public FBI wanted-persons database; retrieves data only, no side effects.
From the tool's definition Browse FBI wanted posters by category, Returns subject detail
Attacks that exploit this kind of access
The rule that runs fbiwanted.persons.by_category 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.by_category, this is the rule to start with:
fbiwanted.persons.by_category 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 Apibase, apply this rule, and every fbiwanted.persons.by_category call is checked against it from then on.
Questions about fbiwanted.persons.by_category
Browse FBI wanted posters by category: Ten Most Wanted Fugitives, Most Wanted Fraudsters, kidnappings, missing persons, seeking-information cases, Endangered Child Alert Program, or law-enforcement-assistance requests. Returns the same subject detail as fbiwanted.persons.search (api.fbi.gov). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
fbiwanted.persons.by_category accepts 3 parameters: page, category, page_size. Required: category. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for fbiwanted.persons.by_category: 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.
fbiwanted.persons.by_category 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 fbiwanted.persons.by_category 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 fbiwanted.persons.by_category. 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.
fbiwanted.persons.by_category 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.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue