get_recent_filings
AI agents call get_recent_filings to retrieve information from Koreafilings without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name follows the 'get/list' pattern typical of Read operations. Within a DART disclosure server, retrieving recent filings is a pure data retrieval action with no side effects. The empty description reduces confidence slightly, but the naming convention and the sibling tool 'list_recent_filings' (which would have identical semantics) confirm this is a Read operation.
From the tool's definition Tool name 'get_recent_filings' indicates retrieval of filing data. Description is empty, but the function name and context of a disclosure database server strongly suggest this queries/lists recent filings without modifying data.
Attacks that exploit this kind of access
get_recent_filings. It is categorised as a Read tool in the Koreafilings MCP Server, which means it retrieves data without modifying state.
Register the Koreafilings MCP server in PolicyLayer and add a rule for get_recent_filings: 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 Koreafilings. Nothing to install.
get_recent_filings 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 get_recent_filings 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 get_recent_filings. 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.
get_recent_filings is provided by the Koreafilings MCP server (oldtemple91/korea-filings-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →