list_sources
AI agents call list_sources to retrieve information from AS400 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to list source code artifacts on an AS400/IBM i system. Per the server description, access is explicitly read-only and limited to metadata and source code retrieval without modification or deletion capabilities. List operations that retrieve data with no side effects fall under the Read category, posing minimal risk if misused by an AI agent.
From the tool's definition Tool name 'list_sources' and server context describing 'read-only access to metadata, source code, and program dependencies'. Sibling tools include 'get_source', 'list_libraries', 'list_programs' which are all retrieval operations.
Attacks that exploit this kind of access
list_sources. It is categorised as a Read tool in the AS400 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AS400 MCP Server MCP server in PolicyLayer and add a rule for list_sources: 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 AS400 MCP Server. Nothing to install.
list_sources 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 list_sources 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 list_sources. 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.
list_sources is provided by the AS400 MCP Server MCP server (kozokaai/as400-mcp). 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 →