Extract all import/require statements from a source file.
AI agents call get_imports to retrieve information from DevToolkit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about dependencies from source files without modifying data, executing code, or causing side effects. It is a straightforward read operation analogous to parsing or querying file contents. The severity is low because misuse would at worst expose information about project dependencies, which presents minimal risk even in an adversarial context.
From the tool's definition Tool name is 'get_imports' and description states it 'Extract[s] all import/require statements from a source file' — a retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
Extract all import/require statements from a source file. It is categorised as a Read tool in the DevToolkit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevToolkit MCP Server MCP server in PolicyLayer and add a rule for get_imports: 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 DevToolkit MCP Server. Nothing to install.
get_imports 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_imports 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_imports. 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_imports is provided by the DevToolkit MCP Server MCP server (tusharrayamajhi/devtoolkit-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 →