get_destination_info

Get detailed information about a specific destination connector.

Server Unstructured API MCP Server liuchongchong1995/uns-mcp
Category Read
Risk class Low
Parameters 00 required

What get_destination_info does on Unstructured API MCP Server

AI agents call get_destination_info to retrieve information from Unstructured API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_destination_info needs a policy

This tool retrieves configuration or metadata about a destination connector without modifying, deleting, or executing any operations. It falls squarely into the Read category as a data retrieval function. The severity is low because accessing connector information poses minimal risk—it does not move data, modify infrastructure, or execute code.

From the tool's definition The tool name 'get_destination_info' and description 'Get detailed information about a specific destination connector' indicate a retrieval operation with no side effects. The verb 'Get' explicitly signals a read-only action that queries existing data.

Questions about get_destination_info

What does the get_destination_info tool do? +

Get detailed information about a specific destination connector. It is categorised as a Read tool in the Unstructured API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_destination_info? +

Register the Unstructured API MCP Server MCP server in PolicyLayer and add a rule for get_destination_info: 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 Unstructured API MCP Server. Nothing to install.

What risk level is get_destination_info? +

get_destination_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_destination_info? +

Yes. Add a rate_limit block to the get_destination_info 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 get_destination_info completely? +

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

get_destination_info is provided by the Unstructured API MCP Server MCP server (liuchongchong1995/uns-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.