Resolve a US stock ticker (e.g. "TSLA") to the SEC's 10-digit CIK identifier — required by every other SEC tool. Call THIS FIRST when you have a ticker and need to use edgar_company_concept, edgar_company_filings, edgar_company_facts, sec_8k_recent, or any other SEC-keyed tool. Returns {cik, cik_...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Edgar server.
Free to start. No card required.
AI agents call edgar_ticker_to_cik to retrieve information from Edgar without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though edgar_ticker_to_cik only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"edgar_ticker_to_cik": {}
}
}See the full Edgar policy for all 25 tools.
These attack patterns abuse exactly the kind of access edgar_ticker_to_cik gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Resolve a US stock ticker (e.g. "TSLA") to the SEC's 10-digit CIK identifier — required by every other SEC tool. Call THIS FIRST when you have a ticker and need to use edgar_company_concept, edgar_company_filings, edgar_company_facts, sec_8k_recent, or any other SEC-keyed tool. Returns {cik, cik_padded, company_name}. Cheap, no rate limit concerns. Most other tools also accept tickers directly and call this internally — only use it explicitly when you want the CIK as data.. It is categorised as a Read tool in the Edgar MCP Server, which means it retrieves data without modifying state.
Register the Edgar MCP server in PolicyLayer and add a rule for edgar_ticker_to_cik: 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 Edgar. Nothing to install.
edgar_ticker_to_cik 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 edgar_ticker_to_cik 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 edgar_ticker_to_cik. 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.
edgar_ticker_to_cik is provided by the Edgar MCP server (https://gateway.pipeworx.io/edgar/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Edgar tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.