A permitted tool reaches the wrong data.
An invoice lookup accepts another customer’s record ID. Authentication succeeds, but the server still needs to enforce ownership and tenant isolation.
oktsec / MCP security
MCP security. Control tool access.
Oktsec helps you inspect MCP servers before adoption and apply policy to tool calls in your environment. Use Signal to review the dependency, Control to enforce runtime rules, or Assessment to test your deployment.
Three ways to secure an MCP deployment.
SignalExplore SignalControlExplore ControlAssessmentScope testing
“Should we approve this server?”
Signal scans supplied source in your browser. Review findings with the rule, location and context behind each detection.
“How do we limit its actions?”
Control applies policy through Oktsec Node, before a routed action executes. Cloud manages policy and the evidence your team reviews.
“Can someone bypass our controls?”
Assessment is a testing service. Get reproducible findings, remediation priorities and a scoped retest of your MCP server.
The protocol connects tools. Your team decides what to trust.
MCP security covers the tools, resources and trust boundaries exposed through the Model Context Protocol. A connected server gives an agent a way to act; its implementation, permissions and responses all belong in the security review.
- The server
- Who maintains it, what runs during installation and which credentials does it receive?
- The caller
- Which user or agent is acting, and what data and operations may that identity access?
- The action
- Does the requested tool, argument or destination stay within that authority?
Look beyond the tool name.
A response changes the task.
A retrieved document asks the agent to read credentials or send a diagnostic export. Treat returned instructions as untrusted and check the actions they trigger.
An approved server changes.
An update adds a shell command, a dependency or broader access. Revisit the version and permissions before relying on the earlier approval.
Local access becomes external access.
A server can read a file and make a network request. Review the combined access, credential scope and allowed destinations—not just each tool separately.
Check the action before the tool executes.
Oktsec Control uses Node inside your environment to apply policy to actions that pass through a supported integration. Cloud coordinates policy and evidence outside the execution path.
- 01 / Request
The agent asks for an action.
The configured integration receives the request and its available identity and tool context.
- 02 / Local decision
Node applies the policy.
The request is allowed, flagged, held or blocked according to the configured rules.
- 03 / Result
The decision leaves evidence.
Permitted requests continue. Blocked requests stop at the enforcement point. The record supports later review.
Requests that bypass the configured integration are outside its enforcement coverage. The MCP server and backing system still need their own authorization checks.
Review deployment and data flowsOne connection. Several places to check.
An agent answering an invoice question should only reach the customer records it is authorized to use. Each layer has a different job.
Security questionWhat your team should checkWhere Oktsec helps
Who is making the request?
Bind the request to the intended identity. The server and backing API must enforce tenant and record ownership.
Assessment tests identity and authorization failures.
What code receives the access?
Review the server version, launch configuration and dependencies before granting credentials.
Signal identifies suspicious instructions and execution patterns in the supplied source.
What action is allowed?
Define which tool calls and parameters belong to the task. Route covered actions through the enforcement point.
Control applies the configured policy locally through Node.
What can we review afterward?
Keep the action, policy decision and available identity context for the period under review.
Node produces signed action evidence; Cloud supports review and export.
Know what was reviewed and what was allowed.
A dependency review and a runtime action record answer different questions. Keep the version and review scope with the approval, then use action evidence to investigate how the deployed workflow behaved.
- Before connection
- Identify the server version, owner, required credentials and accepted permissions.
- During operation
- Review the requested action, policy decision and available identity context.
- After a change
- Revisit affected tools, dependencies and permissions, then test consequential changes.
Understand the MCP security boundary.
Start with a clear answer.
What is MCP security?
MCP security protects the data and actions exposed through Model Context Protocol servers. It includes reviewing server code, authenticating callers, enforcing authorization, constraining tool use and retaining evidence of covered actions.
How do Signal, Control and Assessment differ?
Signal is a product for inspecting supplied agent dependencies in the browser. Control applies runtime policy through Oktsec Node and uses Cloud for policy and evidence workflows. Assessment is a scoped security testing service with findings and remediation.
Does connecting an MCP server make it trusted?
No. Connectivity describes how the client and server communicate. Trust also depends on the implementation, the permissions it receives and the actions it can perform.
Why review tool arguments as well as tool names?
A permitted tool can receive a request outside its intended scope, such as another tenant’s record ID or a sensitive file path. Verify the server’s authorization and configured parameter policy against those requests.
Where does MCP enforcement run?
Control enforces inside the environment where the supported gateway, proxy or integration handles the action. Deployment depends on the MCP client, server transport and workflow.
Give useful tools the right limits.
Bring one MCP client, its server transport and the systems it can access. We will confirm the supported integration, policy requirements and evidence to review in a Control evaluation.