import_terminology · Amazon SageMaker AI MCP Server MCP

WHAT IT DOES

What import_terminology does on Amazon SageMaker AI MCP Server

AI agents use import_terminology to create or update resources in Amazon SageMaker AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon SageMaker AI MCP Server environment.

WHY IT NEEDS A POLICY

Why import_terminology needs a policy

Import operations typically create or modify data reversibly—fitting the Write category. SageMaker imports could affect model training or NLP pipelines, making misuse moderately risky. However, without a description, confidence is reduced. The context (sibling tools like 'aggregate', 'analyze_*') suggests data management rather than destructive operations.

From the tool's definition Tool name 'import_terminology' suggests creating or uploading terminology data into SageMaker (a service for ML model development and deployment). The empty description limits certainty about whether this creates, modifies, or potentially executes operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_terminology Rate-limited

import_terminology stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "import_terminology": {
      "limits": [
        {
          "counter": "import_terminology_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Amazon SageMaker AI MCP Server, so you can run agents against it safely.

FAQ

Questions about import_terminology

What does the import_terminology tool do? +

import_terminology. It is categorised as a Write tool in the Amazon SageMaker AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_terminology? +

Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for import_terminology: 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 Amazon SageMaker AI MCP Server. Nothing to install.

What risk level is import_terminology? +

import_terminology is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit import_terminology? +

Yes. Add a rate_limit block to the import_terminology 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.

How do I block import_terminology completely? +

Set action: deny in the PolicyLayer policy for import_terminology. 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.

What MCP server provides import_terminology? +

import_terminology is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.