This record as markdown: /tools/sankahq-sanka-mcp/get-import-job.md
What get_import_job does on Sanka MCP Server
AI agents call get_import_job to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_import_job is rated Low
This tool retrieves information about an import job by its identifier. The verb 'Load' and the absence of any modification, deletion, or execution language confirm this is a read-only operation. It queries existing data without creating, modifying, or destroying anything. The severity is low because reading job metadata poses minimal risk even if accessed inappropriately.
From the tool's definition Tool name 'get_import_job' and description 'Load one import job by id' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_import_job safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_import_job, this is the rule to start with:
get_import_job 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 Sanka MCP Server, apply this rule, and every get_import_job call is checked against it from then on.
Questions about get_import_job
Load one import job by id. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_import_job: 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 Sanka MCP Server. Nothing to install.
get_import_job 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_import_job 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_import_job. 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_import_job is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue